Kbase P118870: Error 293 when calling a non-persistent AppServer procedure through the Web Services Adapter
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/05/2009 |
|
Status: Verified
SYMPTOM(s):
Error 293 when calling a non-persistent AppServer procedure through the Web Services Adapter
Error 293 when calling an OpenEdge Web Service
** "<file-name>" was not found. (293)
The Web Services Adapter (WSA) is unable to find the r-code in the PROPATH
FACT(s) (Environment):
Calling a non-persistent AppServer procedure
OpenEdge 10.x
All Supported Operating Systems
FIX:
The ProxyGen's PROPATH in relation to the r-code's location is not the same as the AppServer's PROPATH in relation to the r-code's location.
The PROPATH itself might be different between the development and deployment machine, but the relative path for the r-code files below a specified PROPATH directory must remain unchanged. So if the "Propath Components" directory in ProxyGen is not directly pointing to the r-code directory, then a relative path will be used. For example:
Server (WSA, Tomcat, AppServer installed)
AppServer's PROPATH = C:\WS\
Client PC (Web Service Client, Proxy Generator installed)
ProxyGen's PROPATH = C:\Test\
r-code location = C:\Test\WSTest\
Once deployed, the OpenEdge Web Service will be searching for the r-code in C:\WS\WSTest\ on the server, because WSTest is the relative path provided in ProxyGen. If you change ProxyGen's PROPATH to C:\Test\WSTest\ , then no relative path will be used when searching the AppServer's PROPATH.