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.
Summary: | JAX-WS deployment regression | ||
---|---|---|---|
Product: | webservices | Reporter: | tbrantb <tbrantb> |
Component: | JAX-WS | Assignee: | Milan Kuchtiak <mkuchtiak> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | mmirilovic, pjiricka, vkraemer |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
tbrantb
2009-05-27 16:01:20 UTC
are you deploying to v3 Prelude or v3 Preview? Glassfish V3 prelude I cannot reproduce this issue with latest builds. Some time ago I was getting this issue when I had "Deploy on Save" option checked in my project (Project -> Properties -> Run section). Npte: GlassFish V3 Prelude (without Metro plugin) doesn't support J2EE Web Services specification. It behaves like Tomcat server, and requires to have sun-jaxws.xml and some additional entries in web.xml, e.g.: <listener> <listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class> </listener> <servlet> <servlet-name>S</servlet-name> <servlet-class>s.S</servlet-class> </servlet> <servlet> <servlet-name>WebSearchWS</servlet-name> <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>WebSearchWS</servlet-name> <url-pattern>/WebSearchWS</url-pattern> </servlet-mapping> Please check if this configuration stuff was created in your project. To use web services with GlassFish V23 Prelude, I'd recommend to install Metro stack in GlassFish V3 Update Center. I already had the Metro stack installed in glassfish. I tried in the latest nightly and no longer had the problem. I also disabled deploy on save in 6.7 beta and that fixed the problem as well. I am having this problem deploying to Tomcat 5.5. I too am having this problem with NetBeans 6.5.1 and Tomcat 6.0. Disabling deploy on save seems to be a work-around but I wouldn't call it a fix. This was caused by Deploy on Save feature introduced in Netbeans 6.5. The reason for the deployment failure was this. WS from WSDL wizard generates the WS implementation class. Also wsimport generates JAX-WS stub classes, like SEI class into build/generated-sources/jax-ws directory The WS implementation class looks like this : @WebService(serviceName = "WebSearchWS", portName = "WebSearchWSSoap", endpointInterface = "search.WebSearchWSSoap", ..) public class SearchService { public java.lang.String search(java.lang.String keyWord) { ... } } Though, there no compilation dependency on SEI class (search.WebSearchWSSoap), the deployment fails if the SEI class is missing, and it fails with the error reported here. Why this had happened is due to "Deploy on Save" feature. The "feature" thinks that java source files generated in build/generated-sources directory doesn't belong to project and they are not compiled to build/web/WEB-INF/classes. Please, disable "Deploy on Save" in Netbeans 6.5/6.7 if your project contains web services generated from WSDL, or WS clients. I was testing this scenario with latest NB Build (GlassFish V3, Tomcat) and everything works correct. I'm having the same problem with netbeans 6.5.1 and Glassfish 2.1 and just one of my web services. This web service is a wrapper on a ejb. I have an .ear and I realize that I need to force undeploy from server on service tab and then deploy it from project tab. If I just deploy itit fails to generate ws support on server just for that ws. |