How to deploy web service which are not packaged inside a war file in jboss 7

[srimanta.maji]

Actually i want to deploy a soap based web service in Jboss 7. But i am facing following issue.Can anybody suggest me the way of resolving that issue.

The following web service class is inside a jar file which is not pacakged inside the war file.

@WebService(name = "TestService", serviceName = "TestService", portName = "TestService", targetNamespace = "http://services.globalids.com/")

@SOAPBinding(style = SOAPBinding.Style.RPC)

public class TestService {

    @WebMethod

    public void echo(String input) {

        System.out.println("JSEBean01.echo");

    }

}

<servlet>

        <servlet-name>TestService</servlet-name>

        <servlet-class>com.globalids.TestService</servlet-class>

    </servlet>

    <servlet-mapping>

        <servlet-name>TestService</servlet-name>

        <url-pattern>/services/TestService</url-pattern>

    </servlet-mapping>

Issue :

javax.servlet.ServletException: Class com.globalids.TestService is not a Servlet

org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

java.lang.Thread.run(Thread.java:619)

root cause

java.lang.ClassCastException: com.globalids.TestService cannot be cast to javax.servlet.Servlet
     org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
     org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
     org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
     java.lang.Thread.run(Thread.java:619)

[nickarls]

Never tried it but I would start by skipping the web.xml file completely and looking at the @WebContext annotation and see what happens.

[sfcoy]

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.

[sfcoy]

Actually, if it's not packaged in the WAR file, where is it?

[nickarls]

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.

[srimanta.maji]

I am using AS 7.1  final and web service classes are pacakged inside another jar file which is added as a module

[nickarls]

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)