JSR181 EJB endpoint with root contextRoot

[joff]

Hi, I've got an EJB as a JSR181 endpoint, and I want the service to be accessible via a URL like this: http://hostname:8080/MyExampleService?wsdl

This is what I have so far:

@WebService(targetNamespace = "http://example.com", name="MyExample", serviceName="MyExampleService")
@SOAPBinding(style=SOAPBinding.Style.RPC, use=SOAPBinding.Use.LITERAL)
@Stateless
@PortComponent(contextRoot="/", urlPattern="/MyExampleService")
public class MyExampleServiceImpl implements Remote, MyExampleService {
 ...
}

However, deploying it like this results in it apparently (according to the /jbossws/services page) being deployed to http://hostname//MyExampleService?wsdl, but when I click on it, it's gives a 404 error.

Is there any way to successfully get the webservice to deploy in the root?

[jason.greene]

Tomcat has certain restrictions about binding to the root context.

Can you try saying contextRoot="ROOT"? Also make sure you don't have a ROOT.war deployed.

[joff]

Okay, I removed the default ROOT.war, and changed the annotation to read contextRoot="ROOT", but that seems to cause it to ignore the @PortComponent entirely - it deploys to the default /earname-jarname/ context, with the default name.

btw, my application.xml is like this:

<application>
 <display-name>MyExample</display-name>
 <module>
 <web>
 <web-uri>example.war</web-uri>
 <context-root>/</context-root>
 </web>
 </module>
 <module>
 <ejb>example.jar</ejb>
 </module>
</application>

There is no context root specified in the web.xml.

[jason.greene]

Is example.war a servlet deployment? If so, it would conflict with the generated war for the service. Otherwise you don't need that entry.

Can you also try contextRoot=""?

Otherwise, I believe, we may need to add special support for this for EJB endpoints.

http://jira.jboss.com/jira/browse/JBWS-1596

In the meantime you could do with this with a war style deployment.

http://wiki.jboss.org/wiki/Wiki.jsp?page=SetupARootContextApp

-Jason