Right now version 2.0 is like an aircraft at the start of the runway (remember those days before COVID-19?), waiting for the control tower to give final clearance. Will you be an early adopter, downloading the VSIX from GitHub, installing it into your VS Code, and posting back here to confirm that we haven't left anything critical behind at the gate? Then I'll push the throttles forward, publish to Marketplace, and we'll all be on our way.
Server Manager 2.0 is my entry for the current contest. If you like it maybe you'll vote for me it.
Announcing gj :: locate. A simple extension for VS Code that will help you get to the source of your errors.
In VS Code, using either the Serenji extension or the basic InterSystems objectscript extension, this small add-on will open the appropriate class or routine and position you at the exact line where an error occurred.
No more tedious counting of lines to find <UNDEFINED>zCredit+206^Ledger.Invoice.1. Instead, with gj :: locate you can get there with just a couple of clicks.
We want to hear from you! Give us your feedback on the past InterSystems Developer Tools Contest! Please answer some questions to help us improve our contests.
You may think it isn’t too difficult to get from label+offset^routine to the actual source line responsible for the error. For an expert it isn't that hard... most of the time. But there are enough oddities and special rules that even an expert can get it wrong, whilst spending a lot of time trying to get there.
gj :: locate is the latest tool from George James Software – it debugs any error, class or routine by converting the location of an error in compiled .int code to the corresponding location in your source, and then taking you right there.
I have a question about a problem calling a SOAP Web Service.
Indeed, to retrieve data via a Web Service, I need to make 4 calls, one to connect, one to place parameters, one to retrieve data and one to disconnect. Using the EnsLib.SOAP.OutboundAdapter class, I manage to make my first connection call but for the other calls I would need to keep my session cookie otherwise it doesn't consider me as connected. I know it's possible to do this in REST directly in the EnsLib.REST.OutboundAdapter class but I can't find a way to do it in SOAP.
By replies
Open Exchange app
3m read