Search results

You don't mention the OE version, but the from 12.5 onwards, the ABL HTTP tracing feature I linked to can do all of this for you. You'd have to write a class to write the (JSON) trace data to a DB, but all the other bits are part of the OE product.

Sorry, I thought you'd assigned the writer to a variable ... define variable oWriter as OpenEdge.Net.HTTP.Filter.Payload.MessageWriter no-undo. oWriter = objMessageWriterBuilder:Writer. oWriter:Open(). oWriter:Write(RequestObj:Entity). oWriter:Close().

The bit you're missing is doing the writing of the Entity (payload) to the ByteBucket. Passing the message to the Build() method is effectively only doing the set up for the kind of writer to use for that message (ie is it JSON or XML or something else). objMessageWriterBuilder:Open(). /*...

If you're on 12.5+, take a look at Progress Documentation . Alternatively you can do what you're doing and also convert the body to bytes using the BodyWriterBuilder which will give you a bytebucket instance that you can dump to disk.

As @jdpjamesp says, more info would be useful. The first place I'd look is at what caused the STOP condition in the agent.

Per the doc you can for the RUN in any procedure handle. I would create a .P that takes THIS-OBJECT as a input parameter and use that to call back into the class. class DynBrowser: def var hCallbackProc as handle. constructor DynBrowser(): run callback.p persistent set...

I, for one, appreciate your choice of user agent.

Did they indicate what the problem was? Is it in the ABL code or the AVM? If you can avoid shelling out from PASOE you should try to do so. It can become expensive due to the process sizes of the agents.

What's oResponse defined as? WebResponse has the 2-parameter SetHeader() method.

That is indeed the right way to go. Is there a reason you chose not to use oResponse:SetHeader("location", "OAuthFailure.html" ). ? The SetHeader method does the whole building of the HttpHeader object under the covers for you. The other thing to make sure of is that the method returns 0.

Alas, it's not that simple. Unless you want to spend your time writing dynamic code to manipulate temp-tables - and, sure, we all have a somewhat masochistic streak, what with being ABL programmers :D - you will need a temp-table definition in more than one piece of source code. We can argue...

FWIW ALT-L also works in the Riverside VSCode extension. And it is *extremely* hard to avoid include files when you want to use a temp-table definition in more than one program. IMO the price you pay is significantly less than the inevitable errors introduced when you need to edit the TT...

I am not quite so opposed to preprocessors and includes as Julian is, but you should stay well away from using arguments for procedures. They mean that you cannot run on r-code, only source (and are the underlying reason why the data dictionary requires a development license). Please don't go...

I understand that the rcode for VAR is the same as for DEFINE VARIABLE. So you might be able to run rcode compiled in 12.5 or whenever with a 12.2 runtime. Would not recommend or ever suggest that in anything but a toy environment, but might be a fun exercise.

3 letters vs at least 7 (d-e-f-<space>-v-a-r)

If you look at the documentation page for the CREATE BROWSE statement, you'll see an example of a ROW-LEAVE trigger.

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.