Jar files needed when running stand alone Web service client
843833Nov 9 2005 — edited Sep 7 2006I have created a web service using RAD 6. The web service client works fine in RAD but when I try to run it stand alone using java web start it seems to need several Websphere specific JAR files?
I have added all of these:
<jar href="JARs/ATCApp.jar"/>
<jar href="JARs/log4j-1.2.8.jar"/>
<jar href="JARs/rowset.jar"/>
<jar href="JARs/db2java.zip"/>
<jar href="JARs/SQLWebServiceClient.jar"/>
<jar href="JARs/webserviceutils.jar"/>
<jar href="JARs/objectpoolimpl.jar"/>
<jar href="JARs/j2ee.jar"/>
<jar href="JARs/channel.tcp.jar"/>
<jar href="JARs/channel.http.jar"/>
<jar href="JARs/xml.jar"/>
<jar href="JARs/webservices.jar"/>
<jar href="JARs/bootstrap.jar"/>
<jar href="JARs/ras.jar"/>
<jar href="JARs/wsexception.jar"/>
<jar href="JARs/emf.jar"/>
<jar href="JARs/wsdl4j.jar"/>
<jar href="JARs/ffdc.jar"/>
And I finally ran into a No Class Def error, but the error is not referring to any specific class.
ava.lang.NoClassDefFoundError
at com.ibm.ws.webservices.engine.resources.ProjectResourceBundle.<clinit>(ProjectResourceBundle.java:106)
at com.ibm.ws.webservices.engine.resources.MessagesConstants.<clinit>(MessagesConstants.java:93)
at com.ibm.ws.webservices.multiprotocol.resources.Messages.<clinit>(Messages.java:44)
at com.ibm.ws.webservices.multiprotocol.AgnosticService.getStub(AgnosticService.java:387)
at com.principal.corp.apptestcenter.scheduler.sqlWebService.SqlExecuteWSServiceLocator.getSqlExecuteWS(SqlExecuteWSServiceLocator.java:68)
at com.principal.corp.apptestcenter.scheduler.sqlWebService.SqlExecuteWSServiceLocator.getSqlExecuteWS(SqlExecuteWSServiceLocator.java:63)
at com.principal.corp.apptestcenter.scheduler.sqlWebService.SqlExecuteWSProxy._initSqlExecuteWSProxy(SqlExecuteWSProxy.java:24)
at com.principal.corp.apptestcenter.scheduler.sqlWebService.SqlExecuteWSProxy.<init>(SqlExecuteWSProxy.java:9)
at com.principal.corp.apptestcenter.scheduler.sqlWebService.SqlExecute.executeAndGetSQL(SqlExecute.java:96)
at com.principal.corp.apptestcenter.scheduler.databaselayer.ResourceObjDB.getFullTagNameAsMap(ResourceObjDB.java:437)
at com.principal.corp.apptestcenter.scheduler.logiclayer.StaticData.<clinit>(StaticData.java:101)
at com.principal.corp.apptestcenter.scheduler.databaselayer.DomainTableDB.isUserValid(DomainTableDB.java:204)
at com.principal.corp.apptestcenter.scheduler.presentationlayerJava.MainWindow.<init>(MainWindow.java:414)
at com.principal.corp.apptestcenter.scheduler.presentationlayerJava.MainWindow.main(MainWindow.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Why is wsexception.jar needed? Is that not a websphere specific jar file?
What is your experience with this?
Thanks,
David