Hide Forgot
Date of First Response: 2007-11-13 22:02:30 project_key: SOA when tying to run the bin/wsconsume.sh script I get: JBossWS-Native stack deployed Exception in thread "main" java.lang.NoClassDefFoundError: gnu/getopt/LongOpt at org.jboss.wsf.spi.tools.cmd.WSConsume.parseArguments(WSConsume.java:85) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:78)
Seeing the same error with wsprovide.sh sh ./wsprovide.sh JBossWS-Native stack deployed Exception in thread "main" java.lang.NoClassDefFoundError: gnu/getopt/LongOpt at org.jboss.wsf.spi.tools.cmd.WSProvide.parseArguments(WSProvide.java:83) at org.jboss.wsf.spi.tools.cmd.WSProvide.main(WSProvide.java:76)
Is it related to http://lists.jboss.org/pipermail/jbossws-users/2007-June/002380.html
The issue is that the classpath of these scripts assume that the libraries are located in the /client directory. This is true for the full version but not for the standalone one. [kevin@rincewind Desktop]$ unzip -l soa-4.2.0-IR7.0.zip | grep getopt 15858 11-14-07 19:01 jboss-soa-p.4.2.0/jboss-as/client/getopt.jar 15858 11-14-07 19:01 jboss-soa-p.4.2.0/jboss-as/lib/getopt.jar (The above is the version which Trev gave me yesterday and is not the repackaged release) [kevin@rincewind Desktop]$ unzip -l standalone-soa-4.2.0-IR6.0.zip | grep getopt 15860 11-16-07 15:31 jboss-soa-p-standalone.4.2.0/lib/getopt.jar
Assigning to Trev as it is a build issue. This should disappear once we start slimming down the EAP release to create the standalone version.
bash-3.2$ ls standalone-version/lib/getopt.jar standalone-version/lib/getopt.jar
new standalone version based on eap installs it
soa-4.2.0-IR8.0.zip - all config The problems is that JBossWS tools are not probably present in the classpath JBossWS-Native stack deployed Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/tools/ws/wscompile/WsimportTool at org.jboss.ws.tools.jaxws.impl.SunRIConsumerFactoryImpl.createConsumer(SunRIConsumerFactoryImpl.java:36) at org.jboss.wsf.spi.tools.WSContractConsumer.newInstance(Unknown Source) at org.jboss.wsf.spi.tools.WSContractConsumer.newInstance(Unknown Source) at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(Unknown Source) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(Unknown Source)
Link: Added: This issue depends JBPAPP-426
This class occurs in jbossws-native-2.0.1.CP2/thirdparty/jaxws-tools.jar which does not exist in EAP beta 4 and therefore does not make into either SOA version
Heiko I've assigned it to you as the EAP Jira was assigned to you, if it's fixed in EAP we will automatically pick it up
I'll look into it. Sorry for the delay I don't seem to receive JIRA nootifications from this particular project.
It's a build issue. The magic switch (-Dsoa.build=true) misses a great deal build steps required to install 2.0.1.SP2. Please see JBPAPP-426 for more information.