To determine the cause of a Web service problem, check these error log files, which are located in the EAServer bin subdirectory:
Jaguar.log
Jaguarhttpservlet.log
Jaguarhttprequest.log
In addition, if you are using the EAServer Web Services Eclipse plug-in, check the Eclipse file \workspace\.metadata\.log.
Table 6-2 describes the common Web services error messages.
Error message |
Description |
|---|---|
Error 500 Servlet jspservlet: unable to service request: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found. |
Occurs when the xerces.jar file is found in neither the Web application’s class path nor in the EAServer /java/lib subdirectory. |
AxisFault faultCode: Server.userException faultSubcode: faultString: No such operation. |
Verify that you are using the correct datatypes for the parameter values. |
WSTAdminException: com.sybase.wst.admin.WSTAdminException:java.lang.ClassCastException: org.apache.crimson.jaxp.DocumentBuilderFactoryImpl |
This indicates a class loader issue, which can occur when you deploy a Web service if you have specified a dependency class in the deployment descriptor, and the same class was loaded by the EAServer system class loader. To work around this problem, do not include dependency JAR files for third-party libraries to the Web application if those libraries are already provided by EAServer and loaded during start-up. |
