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 155022 - I can't deploy websvc,created without Metro Add-on on Gfv3
Summary: I can't deploy websvc,created without Metro Add-on on Gfv3
Status: NEW
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-09 12:48 UTC by Jaroslav Pospisil
Modified: 2009-02-19 23:29 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Gf v3 server.log (29.44 KB, text/plain)
2008-12-09 12:55 UTC, Jaroslav Pospisil 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2008-12-09 12:48:59 UTC 
Latest daily dev build,JDK1.6.0_10,Win Vista

Create new Java Web App no default server(Gf v3) and create new web service.There'll be info message,
about installation of Metro,but websvc is created successfully,could be deployed etc.
However if I then open Update center of Gf v3 and add Metro, I can't deploy this service anymore.
Comment 1 Jaroslav Pospisil 2008-12-09 12:55:14 UTC 
Created attachment 74743 [details]
Gf v3 server.log
Comment 2 Jaroslav Pospisil 2008-12-09 12:55:48 UTC 
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
wsgen-init:
wsgen-MyWS:
wsgen-service-compile:
Compiling 2 source files to C:\Users\jp154641\Documents\NetBeansProjects\WAGlv301\build\web\WEB-INF\classes
compile:
compile-jsps:
Building jar: C:\Users\jp154641\Documents\NetBeansProjects\WAGlv301\dist\WAGlv301.war
In-place deployment at C:\Users\jp154641\Documents\NetBeansProjects\WAGlv301\build\web
Initializing...
deploy?path=C:\Users\jp154641\Documents\NetBeansProjects\WAGlv301\build\web&name=WAGlv301&force=true&properties=keepSessions=true
running on GlassFish V3
deploy?path=C:\Users\jp154641\Documents\NetBeansProjects\WAGlv301\build\web&name=WAGlv301&force=true&properties=keepSessions=true
failed on GlassFish V3
C:\Users\jp154641\Documents\NetBeansProjects\WAGlv301\nbproject\build-impl.xml:552: The module has not been deployed.
BUILD FAILED (total time: 38 seconds)
Comment 3 Milan Kuchtiak 2008-12-10 10:00:55 UTC 
This issue exists for longer time. De facto web/ejb projects don't listen to changes in target server selection.

It means, for example, when target server is changed from non JSR109 to JSR109, we have to

- remove entries in web.xml
- remove sun-jaxws.xml file
- remove JAX-WS2.1 library from project

... and vice versa, if server is changed from JSR109 to non JSR109, we have to :
- add entries in web.xml
- create sun-jaxws.xml file
- add JAX-WS 2.1 library from project