[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: REST methods returning LONGCHAR results in error

Status
Not open for further replies.
N

Neil Treeby

Guest
I'm not using PASOE because we don't have PASOE licenses right now (apart from the "local" PASOE that comes with PDSOE). Due to issues with a 3rd-party application that aren't scheduled to be resolved until mid-2020 at the earliest (the application is being completely re-engineered as an in-house replacement, but that's not an overnight job), we're stuck with "classic" AppServer for the time being. The error is clearly coming from the Java Open Client libraries so I think you are correct it's coming from Tomcat, somewhere. This issue appears to be restricted to the return values from methods. The following are both okay: /* ping.p */ DEFINE OUTPUT PARAMETER pcReturn AS LONGCHAR NO-UNDO. ASSIGN pcReturn = "okay". /* ping-lib.p */ PROCEDURE ping: DEFINE OUTPUT PARAMETER pcReturn AS LONGCHAR NO-UNDO. ASSIGN pcReturn = "okay". END PROCEDURE.

Continue reading...
 
Status
Not open for further replies.
Top