When you run the JSP Web Services Proxy wizard, you can encounter problems if you select invalid WSDL files.
If you use a WSDL file created by the EAServer Web Services Toolkit, be aware that the toolkit creates two different WSDL files: an interface (or abstract) file and an implementation file. In the JSP Web Services Proxy wizard, you must select the implementation file rather than the interface file to access the Web services described by these files.
The WSDL files that you select must conform to version 1.1 of the WSDL specification found on the W3C Web site.
If you get a class not found error at runtime (typically a provider not found error or a java.lang.NoClassDefFoundError error), make sure all the required JAR files are in your JSP server’s class path. You can find a description of these required files in “Files added by the wizard and files required by the server”.
If you are using EAServer 5.1
With EAServer 5.1,
the required files are already in the server’s class path.
You can copy these files from the Sybase\Shared\PowerBuilder\WEB-INF\lib directory to a directory in your JSP server class path. In EAServer, these files can be copied to the EAServer\java\lib directory, but if EAServer is already running, you must shut down and restart EAServer to make sure they are included in the class path.
Some browsers do not display complete error information returned from the JSP server. If you get a nonspecific runtime error, you may want to test the same JSP in a different browser.
