-
1. Re: How to deploy web service which are not packaged inside a war file in jboss 7
nickarls Feb 13, 2013 1:59 AM (in response to srimanta.maji)Never tried it but I would start by skipping the web.xml file completely and looking at the @WebContext annotation and see what happens.
-
2. Re: How to deploy web service which are not packaged inside a war file in jboss 7
sfcoy Feb 13, 2013 3:22 AM (in response to srimanta.maji)What version of JBoss AS 7 are you using?
The web.xml is optional for JAX-WS based web services in JEE6, so you can probably lose that. However, it should still work correctly even if you have specifed your web service in a web.xml.
-
3. Re: How to deploy web service which are not packaged inside a war file in jboss 7
sfcoy Feb 13, 2013 4:02 AM (in response to srimanta.maji)Actually, if it's not packaged in the WAR file, where is it?
-
4. Re: How to deploy web service which are not packaged inside a war file in jboss 7
nickarls Feb 13, 2013 4:34 AM (in response to sfcoy)Now that you mention it, packaging JAX-WS outside of WAR/EAR is probably non-standard so no gurantees that it will work. Even then, any workaround would probably result in an implicit web app anyway.
-
5. Re: How to deploy web service which are not packaged inside a war file in jboss 7
srimanta.maji Feb 20, 2013 4:54 AM (in response to sfcoy)I am using AS 7.1 final and web service classes are pacakged inside another jar file which is added as a module
-
6. Re: How to deploy web service which are not packaged inside a war file in jboss 7
nickarls Feb 25, 2013 3:56 AM (in response to srimanta.maji)Richard Opalka on #jboss-as7 spake
<opalka> nickarls, considering JBWS-3276 have been implemented in jbossws-cxf-4.0.0.CR1 and
<jbossbot> jira [JBWS-3276] Implement support for POJO endpoints with no web.xml in archive [Closed (Done) Feature Request, Major, Richard
+Opalka] https://issues.jboss.org/browse/JBWS-3276
<opalka> nickarls, AS 7.1.1 final comes with JBossWS CXF 4.0.2.GA
<opalka> nickarls, it should work.
> does it get a context root if deployed in a module?
<opalka> nickarls, the only thing needed is to properly define MANIFEST dependencies in either EJB.jar or WEB.war to include such JBoss module
<opalka> nickarls, you can provide webservices.xml to specify web context
<opalka> nickarls, manifest entry should look like: Dependencies: foo.bar annotations
<opalka> nickarls, where foo.bar is module id
<opalka> nickarls, and annotations means annotations to be imported & to be visible in dependent enterprise archive
<opalka> nickarls, last one thing, such imported JBoss module needs to be jandex-ized (jandex provides ant tool for that)