The following are known problems and workarounds to run the Web services samples.
When installing the EAServer Web services samples into Eclipse, you may see errors related to the following issues.
(CR #341509) You will see several errors caused by the lack of Web service client classes that must be generated after importing. This is expected, since the client classes must be generated for each sample project according to the readme files that accompany each sample.
(CR #341533) You see errors for unresolved javax.ejb dependencies when importing the EJBSample. This sample is not intended to be built or used in Eclipse, but is rather meant to be compiled manually and then deployed to EAServer using EAServer Manager. EJBSample contains the source code for an EJB and requires classes that Eclipse does not have, such as javax.ejb.*. To eliminate error messages caused by the unresolved dependencies, right click on the EJBSample node, choose the Properties menu item, choose Java Build Path on the left pane of the resulting dialog, select the Libraries tab on the right pane, click the Add External JARs button and choose $JAGUAR/java/lib/easj2ee.jar, which will add in the javax.ejb.* classes into the path for that project.
(CR #346072) When running the CanineShelter sample, you may see the following error when performing the README step “Deploying the SoapDemo.jar as a WebService”:
BUILD FAILED java.lang.VerifyError: (class: org/apache/tools/ant/types/Path$PathElement, method: <init> signature: (Lorg/apache/tools/ant/types/Path;) Expecting to find object/array on stack
To workaround this problem, modify the script $JAGUAR/bin/jagant to run JDK 1.4 instead of JDK 1.3. Change the line:
JAVA_HOME=$JAGUAR_JDK13/jre export JAVA_HOME
To:
JAVA_HOME=$JAGUAR_JDK14/jre export JAVA_HOME
| Copyright © 2004. Sybase Inc. All rights reserved. |
|
|
