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 216219 - WS from WSDL contains wrong pointer to WSDL
Summary: WS from WSDL contains wrong pointer to WSDL
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Denis Anisimov
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2012-07-31 20:40 UTC by Lukas Jungmann
Modified: 2012-08-09 02:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (186.54 KB, image/png)
2012-07-31 20:43 UTC, Lukas Jungmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2012-07-31 20:40:28 UTC
Product Version: NetBeans IDE Dev (Build 20120731-eec09b527313)
Java: 1.7.0_04; Java HotSpot(TM) 64-Bit Server VM 23.0-b21
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
User directory: D:\Java\_nb_dev\udir
Cache directory: D:\Java\_nb_dev\udir\var\cache


-deploy this app to GF-v4: http://java.net/jira/secure/attachment/50106/jaxws-w2j-03-web.war (src is available here: http://java.net/jira/secure/attachment/50107/src.zip)

-create new web app
-create a web service from WSDL using WSDL of previously deployed ws (http://localhost:8080/jaxws-w2j-03-web/addnumbers?wsdl )

-deploy the web app

=> fails because IDE generates @WebService.wsdlLocation = "WEB-INF/wsdl/SomeTest/SomeTest.wsdl") but WSDL itself is packaged/available in "WEB-INF/wsdl/SomeTest/localhost_8080/jaxws-w2j-03-web/addnumbers.wsdl"

-fix the @WebService.wsdlLocation
-deploy app again
-open ws tester

=> quite hard to find this action since there's no web service node visible in the project view
Comment 1 Lukas Jungmann 2012-07-31 20:43:18 UTC
Created attachment 122602 [details]
screenshot
Comment 2 Lukas Jungmann 2012-07-31 22:37:53 UTC
note that this happened with fresh IDE build with new usedir

another observation/issue:

when I realized that there's no visible ws node, I checked nbproject/jax-ws.xml and it contained all necessary entries, so I continued in my work, which was:
-create a client for this new service (using WSDL URL because of missing node in from project option), run it and debugged jaxws-ri in GF-v4.

At some point I needed to update the ws impl class and re-deploy the app (which already had compile-on-save disabled) but suddenly I wasn't able to build and deploy the project anymore - all ws related info was(silently) deleted(!) (=no build scripts, empty nbproject/jax-ws.xml), only my ws impl class remained untouched by the IDE.

As soon as I recreated the service, everything started working correctly - ws node becomes visible, ws impl class had correct wsdlLocation attribute, no dataloss appeared after a bit of work.
Comment 3 Denis Anisimov 2012-08-07 12:23:27 UTC
I'm able to reproduce it.
Deployment is not possible because of wrong WSDL file path.
Comment 4 Denis Anisimov 2012-08-07 12:30:48 UTC
Fix for absent WS node after WS creation via wizard.
web-main#24370daa218a
Comment 5 Quality Engineering 2012-08-08 02:34:45 UTC
Integrated into 'main-golden', will be available in build *201208080001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/24370daa218a
User: Denis Anisimov <ads@netbeans.org>
Log: Partial fix for BZ#216219 : absence on WS node after its creation via wizard.
Comment 6 Denis Anisimov 2012-08-08 06:31:35 UTC
Wrong wsdl file is in the annotation at the very first time of wizard work.
All subsequent invocations set the correct WSDL path.

Wrong behavior is a subsequence of inability to find service by id in the JaxWsModel. I need to investigate the reason.
Comment 7 Denis Anisimov 2012-08-08 09:43:13 UTC
I lower the priority because :
- this is not a regression: nothing is changed.
This bug has been always there.
- it is corner case and it is reproducible in only very specific case.
It is a consequence of initial WS cleanup when project is opened: project open 
hook removes all WS entries from the XML file which are not recognized as a WS
on the FS.
So the issue appears only when WS is created in the model ( in XML file ) but not
yet on the FS and project open hook is doing
Comment 8 Denis Anisimov 2012-08-08 14:56:02 UTC
web-main#9ee7023f57f2
Comment 9 Quality Engineering 2012-08-09 02:39:20 UTC
Integrated into 'main-golden', will be available in build *201208090001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/dead7851df4d
User: Denis Anisimov <ads@netbeans.org>
Log: Fix for BZ#216219 - WS from WSDL contains wrong pointer to WSDL.