users@jax-rpc.java.net

Re: wsdeploy and "-classpath" option

From: Ted o Donovan <ted.odonovan_at_ECET.COM>
Date: Mon, 14 Oct 2002 04:35:51 -0600

Hi,

Thanks for that prompt reply. I set the classpath but now it wont compile for me? I got a No class def found error, i.e.

info: created temporary directory: C:\jwsdp-1_0_01\docs\tutorial\examples\jaxrpc
\hello\build\wsdeploy-generated\jaxrpc-deploy-ff22c6
info: processing endpoint: MyHello
info: removed temporary directory: C:\jwsdp-1_0_01\docs\tutorial\examples\jaxrpc
\hello\build\wsdeploy-generated\jaxrpc-deploy-ff22c6Error: null

java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: com
/ecet/util/data/PrincipalId
        at java.lang.Class.getMethods0(Native Method)
        at java.lang.Class.getMethods(Class.java:742)
        at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.processInterface(Rmi
Modeler.java:268)
        at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler
.java:231)
        at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.buildModel(RmiModele
r.java:194)
        at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:
77)
        at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
        at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:359)

        at com.sun.xml.rpc.tools.wsdeploy.DeployTool.process(DeployTool.java:219
)
        at com.sun.xml.rpc.tools.wsdeploy.DeployTool.process(DeployTool.java:202
)
        at com.sun.xml.rpc.tools.wsdeploy.DeployTool.run(DeployTool.java:182)
        at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:41)C:\jwsdp-1_0_01\docs\tutorial\examples\jaxrpc\hello

However what I just noticed is that if I remove the "c:" in my classpath wsdeploy works. i.e.

wsdeploy -classpath /dev/common/lib/util/ecetutil.jar ....

However the war file generated puts my generated classes in the following directory:

web-inf\classes;\dev\common\lib\util\ecetutil.jar\com\ecet\util\data

i.e. it is using the classpath as the appending path for the destination of the generated files? My previous error was because i was using the "c:" which fails on windows.

I can only guess that this is a unix 2 windows bug?

I think the reason it compiles for you is that if the jar file resides in the common\lib directory of the web services pack it will pick that up and compile/preprocess using that, and not the classpath env variable. This could cause trouble however if the latest version of the jar was not copied into the lib directory prior to wsdeploying.

T.