[
https://issues.apache.org/jira/browse/GERONIMO-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reopened GERONIMO-3831:
-----------------------------------
Assignee: Jarek Gawor (was: David Jencks)
Looks like some of these changes broke jaxws-tools command line tool.
[EMAIL PROTECTED]:~/target>
geronimo-tomcat6-jee5-2.0.3-SNAPSHOT/bin/jaxws-tools.sh wsgen
Using GERONIMO_BASE: /home/jgawor/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT
Using GERONIMO_HOME: /home/jgawor/target/geronimo-tomcat6-jee5-2.0.3-SNAPSHOT
Using GERONIMO_TMPDIR: var/temp
Using JRE_HOME: /home/jgawor/software/jdk1.5.0_12/jre
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/geronimo/common/DeploymentException
at
org.apache.geronimo.jaxws.builder.JAXWSToolsCLI.main(JAXWSToolsCLI.java:50)
> Incomplete classpath fed to wsgen
> ---------------------------------
>
> Key: GERONIMO-3831
> URL: https://issues.apache.org/jira/browse/GERONIMO-3831
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.1, 2.1.1
> Reporter: David Jencks
> Assignee: Jarek Gawor
> Fix For: 2.0.x, 2.1, 2.2
>
> Attachments: GERONIMO-3831-2.patch, GERONIMO-3831-2a.patch,
> GERONIMO-3831-3.patch, GERONIMO-3831-branches-2.0.patch, GERONIMO-3831.patch
>
>
> The code in WsdlGenerator is only looking at the current configuration when
> constructing a classpath to feed to wsgen. If you have an ear with a ws in a
> war that uses classes in the ear lib or an ejb jar this won't be enough. I
> think the solution is to include all the ancestors....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
