Search results

There is a setting in the project settings that relates to "Modules" that I think may impact this path. Make sure that the AppServer folder is selected.

The Procedure Editor will use whatever settings the session is using. So you could add a file using the command line (Progress Documentation)

Check syntax does a compile behind the scenes :)

Ah, ok. The code documentation procegrams will include INPUT/INPUT-OUTPUT/OUTPUT as well as the datatype of the parameters. This is not done by the code documentation tools. They will look at the comments on the procedure and generate the documentation based on that.

You can automate which programs call which programs using the COMPILE XREF functionality. The compile XREF can tell you who calls who, as well as the parameters. I'm not sure what you are looking for here. For this, as well as probably the example of calling, you are going to want to look at...

This often means that you don't have the root CA certificate. You can see what that is using your browser (usually via clicking on the lock next to the URL bar). In this case, it's Go Daddy Root Certificate Authority - G2 . You should download and install that in the certs dir.

It's a hallucination. You can use an openclient (java or .NET) to call ABL on an AppServer. You can call .NET classes from ABL clients (over the "bridge"). You can call java classes that are exposed via something like the IKVM in .NET. But you cannot call java classes directly in ABL. In 12.8...

If you have the developer tools license you have access to both Appbuilder and PDSOE (Progress Developer Studio for OpenEdge, fka OE Architect). I'd assume this is the "OE Studio" your partner is referring to. You should have access to it - it's been in the OE product for many releases/years...

IMO PDSOE is notoriously flaky when publishing stuff. Some people have the correctly-coloured thumb to be able to publish consistently; I don't. If you're adding a webhandler to an 11.7 PASOE instance, and have access to the server, I would just add the handler line to conf/openedge.properties...

In addition to what @Stefan says, you will also replace your wtbman call with tcman (or pasman).

The WSA has moved into PASOE in OE 12.0+ . The "Classic" AppServer was removed from OpenEdge in 12.0 and replaced by PASOE. PASOE is also a Tomcat server, and you can deploy SOAP services to it using the same artifacts as for the WSA.

Why? Are there any significant differences between the executables or environments? The OP's command line should use the -b switch, for sure.

No. OE Explorer is completely separate from PASOE. Not sure why you would be seeing Tomcat login info . What URL are you requesting?

Shortest answer: yes. Longer answer: PASOE *is* a Tomcat install. So when you create what's called an instance, you are using a version of Tomcat that's installed together with OpenEdge. You do not need a separate install of Tomcat.

The AVM will undo any transactions that were started during that giant DO TRANSACTION block. You can be 100% of that .... Progress has had 40 years of practice making sure that this works as expected. There are other non-transaction things you can do like read/write files to disk, make...

You can save yourself some typing and just use the GUID function without an argument. The GUID function also returns a character value, so you don't need to use the STRING function either. ttContacts.ContactID = GUID. /* Auto-generate ContactID *

Ok, what heppens if you do just this? No extra headers. oRequestBody:Encoding = 'utf-8'. oRequest = RequestBuilder:Post(oUri, oRequestBody) :ContentType('text/xml; charset=utf-8') :AcceptAll() :AddHeader('SOAPAction'...

This is how you set it , or shold set it. oRequest = RequestBuilder:Post(oUri, oRequestBody) :ContentType('text/xml; charset=utf-8') :AcceptAll() :AddHeader('SOAPAction', 'http://tempuri.org/IConsultaCFDIService/Consulta')...

You were doing this earlier, and got the same error. Or? If so, that tells me that the server does not like the quoted charset. oRequest = RequestBuilder:Post(oUri, oRequestBody) :ContentType('text/xml; charset=utf-8') :AcceptAll()...

Ok, it looks like the server does not like the quoted charset value (even though that's legal HTTP). You can try @Cecil 's suggestion to leave off the charset completely. That may work. Getting rid of the quotes is more complicated ... the Http Client always quotes header parameter values...