[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: JSDO not working as advertised

[ssouthwe]

The problem turned out to be that my service catalog, the .json file, did not have a "schema" section in it for my BE. In my BE, at the top of the file, my annotation looked like this: @progress.service.resource FILE(name="BEWebUser", URI="/BEWebUser", schemaName="dsWebUser", schemaFile="bewebuser.i"). But it needed to look like this: @progress.service.resource FILE(name="BEWebUser", URI="/BEWebUser", schemaName="dsWebUser", schemaFile=" Ingrid/PASOEContent/WEB-INF/openedge/ bewebuser.i"). Once I fixed it and then opened and saved the service definition, it deployed a new catalog that included the "schema" element: Once that was in place, the JSDO began to act correctly as documented. Thanks Edsel!

Continue reading...