P
Peter Judge
Guest
The challenge with handlers is that not only must they be in order but the N in handlerN MUST be sequential without gaps. The other challenge with the web transport is that we (with one exception) do not tie the ABL service name you provide in PDSOE to any part of the URI. So you can create a /web based service called “RandomServiceName” and with a handler, and add /foo and /bar as URIs for it and the service name is NOT added to the URIs (and thus handler definitions in the properties file). I would recommend that you add the ABL service name to the URI mappings so that you can have better control over your URIs; this should also make for easier renaming We are currently working on improvements in the definition and deployment of ABL services which aim to address these and other issues around /web based ABL services. FWIW, PDSOE creates an intermediary file that it sends top the server and applies there (adds to the openedge.properties file). From memory that contains a handler name and the URIs it handles. I don’t know how that file is applied to the oe.props file (ie appended or prepended etc)
Continue reading...
Continue reading...