This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 87640 - Creating WS client from WSDL URL in a EJB3 Module does not work
Summary: Creating WS client from WSDL URL in a EJB3 Module does not work
Status: RESOLVED DUPLICATE of bug 90381
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-20 14:06 UTC by gmichalke
Modified: 2007-07-18 19:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gmichalke 2006-10-20 14:06:25 UTC
Testing 5.5 RC2

When I create, with the NB GUI, in a J2SE project, a WS Client from a WSDL URL,
everything works OK

When I create a WS Client, with the same WSDL URL, from within an EJB JEE5
Module, I get the following error:

init;
wsimport-init: PRJPATH/My-ejb/nbproject/build-impl.xml:224: taskdef class
com.sun.tools.ws.ant.WsImport cannot be found
BUILD FAILED (total time: 0 seconds)
Comment 1 Lukas Jungmann 2006-10-20 14:10:20 UTC
Which target server do you use?
Comment 2 gmichalke 2006-10-20 14:28:35 UTC
I use JBoss 4.0.4GA
Comment 3 Lukas Jungmann 2006-10-20 14:38:41 UTC
Add JAX-WS 2.0 and JAXB 2.0 libraries to your project, it should work then.
Comment 4 gmichalke 2006-10-23 08:50:16 UTC
Helas not...

I added the JAXWS 2.0 and the JAXB 2.0 libraries to the project, but without any
success.

When I deploy to SJAS9 aka Glassfish, it works OK, but I need it to work with JBoss
Comment 5 Lukas Jungmann 2006-10-24 15:14:36 UTC
well, so add also following target to your project's build.xml:

    <target name="-post-init">
        <property name="j2ee.platform.wsimport.classpath"
value="${javac.classpath}"/>
    </target>
Comment 6 Lukas Jungmann 2007-07-18 19:25:37 UTC

*** This issue has been marked as a duplicate of 90381 ***