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 102436 - Error during ws client creation on TC5.5
Summary: Error during ws client creation on TC5.5
Status: VERIFIED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P1 blocker (vote)
Assignee: Roderico Cruz
URL:
Keywords: RELNOTE
Depends on: 100718
Blocks:
  Show dependency tree
 
Reported: 2007-04-25 09:05 UTC by Jaroslav Pospisil
Modified: 2007-04-27 13:06 UTC (History)
2 users (show)

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 Jaroslav Pospisil 2007-04-25 09:05:42 UTC
build 200704231800,JDK 1.6.0_01,Tomcat 5.5.17

1)Start IDE with new userdir
2)Add TC5.5 in Runtime tab
3)Create new web module on Tomcat
4)Add web service client (use this wsdl:
http://www.esynaps.com/WebServices/SearchWS.asmx?WSDL )
4)ERROR: Build fails

generating code...
wsc\ObjectFactory.java
wsc\Search.java
wsc\SearchResponse.java
wsc\WebSearchWS.java
wsc\WebSearchWSSoap.java
wsc\package-info.java
C:\Documents and Settings\Telco\My
Documents\NetBeansProjects\WebApplication6\build\generated\wsimport\client\wsc\WebSearchWS.java:10:
cannot find symbol
symbol  : class WebServiceFeature
location: package javax.xml.ws
import javax.xml.ws.WebServiceFeature;
C:\Documents and Settings\Telco\My
Documents\NetBeansProjects\WebApplication6\build\generated\wsimport\client\wsc\WebSearchWSSoap.java:8:
cannot find symbol
symbol  : class XmlSeeAlso
location: package javax.xml.bind.annotation
import javax.xml.bind.annotation.XmlSeeAlso;
C:\Documents and Settings\Telco\My
Documents\NetBeansProjects\WebApplication6\build\generated\wsimport\client\wsc\WebSearchWSSoap.java:20:
cannot find symbol
symbol: class XmlSeeAlso
@XmlSeeAlso({
C:\Documents and Settings\Telco\My
Documents\NetBeansProjects\WebApplication6\build\generated\wsimport\client\wsc\WebSearchWS.java:62:
cannot find symbol
symbol  : class WebServiceFeature
location: class wsc.WebSearchWS
    public WebSearchWSSoap getWebSearchWSSoap(WebServiceFeature... features) {
4 errors
compilation failed, errors should have been reported
C:\Documents and Settings\Telco\My
Documents\NetBeansProjects\WebApplication6\nbproject\build-impl.xml:308:
wsimport failed
BUILD FAILED (total time: 4 seconds)

NOTICE: This issue is related to space in NetBeans 6.0 installation path, since 
when NetBeans 6.0 is installed into path without spaces, it works O.K.
Comment 1 Milan Kuchtiak 2007-04-26 00:05:33 UTC
I investigated the problem and found out the following :
if jax-ws is used from IDE, jvmarg for java.endorsed.dirs needs to be specified
for wsimport, in addition to xendorsed attribute:

The solution :
<wsimport fork="true" xendorsed="true" ....>
  <jvmarg value="-Djava.endorsed.dirs=${jaxws.endorsed.dir}"/>
</wsimport>

This should be implemented for both web project and Client Application Project.


Comment 2 Roderico Cruz 2007-04-26 06:13:16 UTC
Fixed the web project xsl script to add jvmarg attribute to the wsimport call.
Did the same for the App Client. Additional fix had to be done on the App Client
because the wsimport classpath was not being set in the private properties.
Comment 3 Jaroslav Pospisil 2007-04-26 14:58:24 UTC
I just tested the supposed fix and I'm afraid it won't work, because all
possible combinations of fork and xEndorsed and jvmarg don't work in build 20070426.

Only reliable workaround for this is to copy jaxws-api.jar and jaxb-api.jar from
IDE to $JAVA_HOME/jre/lib/endorsed folder.
Comment 4 Jaroslav Pospisil 2007-04-26 15:00:14 UTC
See my comments above. Reopening.
Comment 5 Petr Blaha 2007-04-26 17:02:52 UTC
This is same root cause as in issue #100718. The bug is in 3rd party library.
The workaround is mentioned in this issue and will be in release notes.
Comment 6 Jaroslav Pospisil 2007-04-26 18:12:39 UTC
I'm taking back previous statement - I made a mistake in applying the patch and
now I verified, that correct form of patch works.Closing issue as fixed and I
apologize to Rico for misunderstanding.
Comment 7 Jaroslav Pospisil 2007-04-27 08:17:52 UTC
Verified in 200704261200
Comment 8 _ rkubacki 2007-04-27 13:01:53 UTC
This is fixed but I can't find in what build - can you set 'Target milestone'?
Comment 9 Milan Kuchtiak 2007-04-27 13:06:23 UTC
Was fixed before M9 branch was created