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 49514

Summary: taskdef class com.sun.xml.rpc.tools.ant.Wscompile cannot be found
Product: webservices Reporter: Petr Blaha <blaha>
Component: CodeAssignee: Roderico Cruz <rcruz>
Status: VERIFIED FIXED    
Severity: blocker CC: athompson
Priority: P2 Keywords: RELNOTE
Version: 4.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Attachments: test project

Description Petr Blaha 2004-09-24 09:09:21 UTC
[Build 040924]
Steps:
1) start NB with empty userdir 
2) create simple web project with simple web
service client
2) build project
3) exit NB
4) remove user dir and start NB
5) open project
6) build
Get build error:
/home/pb151311/space/progr/testing/SimpleClient/nbproject/build-impl.xml:176:
taskdef class com.sun.xml.rpc.tools.ant.Wscompile
cannot be found
Comment 1 Petr Blaha 2004-09-24 09:10:05 UTC
Created attachment 17856 [details]
test project
Comment 2 _ pcw 2004-09-26 06:18:33 UTC
Rico - Due to my latest change to the web service / client build
system, this bug probably will manifest differently, namely that
Javac.class won't be found.  Assuming I'm correct, the solution is
unclear.  The remaining entry in userdir\build.properties is for
tools.jar and is designed to be user-modifiable for EA1 so that we
don't mess up Mac people in case they need to change it to something else.
Comment 3 _ ludo 2004-10-03 00:37:02 UTC
any new status on this one?
Not EA1? or not reproducible
Comment 4 Roderico Cruz 2004-10-03 01:18:12 UTC
This is reproducible, but is not for EA1. As indicated in Peter's
comment, due to the change in the build system, the bug now manifests
itself differently, namely, javac could not be found. Have to dig some
more for a solution to this.
Comment 5 Petr Blaha 2004-10-13 10:40:11 UTC
Remove all issues from temporary component.
Comment 6 _ ludo 2004-10-25 01:25:08 UTC
Workaround for now, if you have this error:
...
[wscompile] error : com.sun.tools.javac.Main is not available in the
classpath..
[wscompile] error: compilation failed, errors should have been reported

The workaround is to create a new web project and build and then try
build your previous project.

This will restore in the file $HOME/build.properties, the attribute
"wscompile.tools.classpath" which is not updated with the proper
information until the ide creates a new service.
Comment 7 Petr Blaha 2004-10-25 08:29:57 UTC
WORKAROUND NOTE: create a new web project, add to new project web
service and build and then try build previous project. 
User must create new project with web service.
Comment 8 _ pcw 2004-11-11 20:00:32 UTC
*** Issue 51104 has been marked as a duplicate of this issue. ***
Comment 9 Roderico Cruz 2005-01-18 12:15:57 UTC
Fixed.
Comment 10 Lukas Jungmann 2005-01-18 13:52:46 UTC
RELNOTE keyword applies only to EA2.

--lukas
Comment 11 Lukas Jungmann 2005-02-17 13:09:56 UTC
v. 200502170805
Comment 12 athompson 2005-07-26 23:46:48 UTC
i'm getting this same error now if i try to compile any web app with web
services and the server set to tomcat. if the server is set to sun app server it
compiles fine.

jdk-1.5
linux
daily 25 july 2005
Comment 13 Geertjan Wielenga 2005-07-27 07:48:00 UTC
Please read the in-product help system before creating an issue. There is a
fairly large help section on Web Services. In the topic "Preparing to Develop
Web Services and Clients", you will find the following:

"The IDE uses the wscompile tool to compile web services and web service
clients. The wscompile tool is bundled with the Sun Java System Application
Server (SJS Application Server). You cannot compile a web service or a web
service client unless the SJS Application Server is the target server for the
project."
Comment 14 athompson 2005-07-27 15:31:18 UTC
i'm sorry; i thought i did a good job of searching for an anwer to this problem
(that's how i found this issue), but i missed that.

i am unfortunately not an expert of this stuff but that brings up the obvious
point: if you can't compile web services for tomcat, why does netbeans allow you
to add them? is there something i'm not understanding? i could have sworn i
remembered there was a tutorial for this in 4.0. i'm sorry for wasting your
time, but i need to create a web service for tomcat and i'm lost. any
documentation you can point me to would be greatly appreciated. if you point me
in the right direction, i'll send you a 6-pack of your choice of inexpensive beer!
Comment 15 Lukas Jungmann 2005-07-27 15:40:47 UTC
That tutorial you've mentioned is still there, just point your browser at
http://www.netbeans.org/kb/articles/tutorial-webservice-40.html :)
Comment 16 clever 2005-09-08 16:38:45 UTC
I'm using verion 200508251800 build and I'm getting the same problem after
targeting a jBoss server.  I looked at the URL listed and couldn't find any
mention of the 'wscompile' requirements, except for the modification to
build.xml.  In that build file, the target points to com.sun.xml.rpc...  Is
there any way to point the IDE to a wscompile that it part of the required WSDP?

I have added the mentioned libraries to a newly created 'JAX-RPC' library, and
the build still fails.  The actual error is:

taskdef class com.sun.xml.rpc.tools.ant.Wscompile cannot be found
BUILD FAILED (total time: 0 seconds)

As mentioned, this did work with Sun App Server. I'm trying to switch to jBoss,
because the relative time it takes to reload a changed class with JAS is just
too much.

I am unable to find a solution. "Use Sun App Server" is no solution. It defeats
the purpose of supporting other containers.
Comment 17 Petr Blaha 2005-09-08 17:00:21 UTC
Hi,
Jboss plugin doesn't support web service yet. We filed a new enhancement, see
#63326.
Comment 18 Lukas Jungmann 2005-09-08 17:07:22 UTC
or add following target to your build.xml:

<target name="-pre-init">
    <!-- property libs.jaxrpc16.classpath is defined in
$USERDIR/build.properties -->
    <property name="j2ee.platform.wscompile.classpath"
value="${libs.jaxrpc16.classpath}"/>
</target>

and copy JAXRPC libraries to your server's lib dir
Comment 19 Geertjan Wielenga 2005-09-08 17:18:37 UTC
The above solution is probably the best for now. Here's another one:
http://blogs.sun.com/roller/page/geertjan/?anchor=deploying_web_service_clients_to
Comment 20 Petr Blaha 2005-11-04 12:35:27 UTC
Original issue was fixed and verified in b. 200502170805