Search results

This might be related (in a broad sense) to Progress Documentation . At one point the ability to have a governor on the agent memory was discussed, but it is not in the product. I wonder whether this Swagger doc is simply inaccurate documentation.

How is the PASOE instance started? Under which user?

.war files are a whole other beast. And you don't need PDSOE for them either. It's almost only for producing PAAR files that you need PDSOE.

PASOE source code is just ABL source code. No need for anything special to compile it. What you DO need PDSOE for, is for creating certain kinds of service artifacts (eg REST API).

It's less "clever" and more "enjoys suffering" :D

You should be aware that 11.6 - and tomorrow, all 11.x releases - is retired. The example you have in the attached hello.p looks like Classic WebSpeed code. It will not work with restbroker (aka the Rest Adapter aka the REST transport in PASOE). A simple program to return data for the rest...

The doc at Progress Documentation is also very good - it describes various configuration properties including how they relate to each other (especially important w.r.t timeouts).

Is there a central repo for smtpmail? Or is it truly distributed source control :P

If you want to continue using the PUT statement and want the data quoted, look at the QUOTER function. For you old 'uns here, is there any other example you can think of of a language function being 'imported' from a C program that Progress ships?

The output that you are showing is for different tables I assume. Are you sure they use the same program to write the data to disk? The first example might be using a PUT or DISPLAY statement, and not the EXPORT statement.

It looks like you are missing the "transport" part of the request URI. That will be something like /rest/ or /web/ .

That was one of the structural changes I mentioned ... in 12.5 (I think) the type went from ByteBucket to RawMessage to support HAR tracing. The principle's the same, just make sure you use the correct version. You may nee to typecheck before casting if you want to use this class in 11.7 and 12.8..

A way to provide an override is as follows: 1. Create a class that extendes OpenEdge.Net.HTTP.Filter.Payload.DefaultRequestFilter (inherits from). 2. Override the WriteStartLine method. Copy & paste the original method in, and remove the lines that check for the existence of a proxy. DO NOT CALL...

It almost looks like there _was_ a bug in the 11.7 code which did not write the correct POST line. But it's hard to tell without some more debugging (I know that's just a variation on 'it depends'). Which exact 11.7 are you seeing the "good" behaviour in?

I would not have expected a behaviour change in this regard. There are some internal changes to the data structures used (and obviously other changes for various things) but the code that writes the start line URL has not changed between 11.7 and 12.8 as far as I can tell. // In...

The CONNECT request is (only) sent when proxying over https, so you should be seeing it in your case. You are not going to see that request written into the request and response txt files (or rather, they will be overwritten), but if you set the LOG-MANAGER LOGGING-LEVEL to 5 then you will see...

The PDSOE versions will be the OpenEdge version. So for 12.8 you will have version 12.8. The Eclipse version is whatever it is. You will need to get the installer from Progress' ESD site .

This is because the static code is loaded once per session and you cannot unload or force a reload. When you are testing, I would strongly recommend that you use a separate session/shortcut. That way you know that you are working on the most recent code. If you follow @Osborne 's suggestion...

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)