[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1622) Multiple context root not supported

Rick Reumann (JIRA) jira-events at lists.jboss.org
Mon May 14 16:31:52 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBWS-1622?page=comments#action_12362211 ] 
            
Rick Reumann commented on JBWS-1622:
------------------------------------

Can someone please more specific about what needs to be done to address this issue? This is very frustrating since I see nothing about this issue in the users guide. 

Here was an example of an initial web service I was trying to deploy (which works fine, until I try to deploy another webservice using the same approach):

@WebService 
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
public interface Echo {
	@WebMethod String testEcho(String s);
}

@Stateless
@WebService(endpointInterface="com.foobar.edsf.example.ejb.webservices.Echo") 
public class EchoBean {
	 public String testEcho(String s) {
		 return s;
	} 
}

If I deploy a similar webservice like the above, I'll get the Multiple context root not supported error. Am I doing something unorthodox or is this a bug? My EJB3 book and the examples that come with the jboss patch here: http://docs.jboss.org/ejb3/app-server/tutorial/installing.html  show examples like I'm doing above.  Now it seems like I have to use a non-standard @WebContext annotation? I can deal with using the @WebContext annotation but can someone give specifics on how to use it to handle this problem?

WITHOUT adding a @WebContext I'll end up with a wsdl location like:

http://machine-name:8080/EchoBeanService/EchoBean?wsdl

If I try to declare a @WebContext  I won't get the multiple context root error, but it changes the wsdl path to a path that it can't find. For example if I give it a path:

@WebContext(contextRoot="/EDSF-tests", secureWSDLAccess=false)

I end up with a wsdl URL:

http://machine-name:8080/EDSF-tests/EchoBean?wsdl

Which doesn't point to the wsdl anymore. Can someone give me some pointers about what I'm doing wrong? Thanks




> Multiple context root not supported
> -----------------------------------
>
>                 Key: JBWS-1622
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1622
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: jbossws-1.2.1
>         Environment: JBoss 4.0.5 + EJB3 + JBossWS 1.2.1.GA
>            Reporter: Stephan Heffner
>
> Switching JBossWS from 1.2.0.SP1 to 1.2.1.GA I got this error message starting my EAR based application including four Services:
> 09:36:13,998 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: joe.ear/joe.jar
> 09:36:14,001 ERROR [MainDeployer] Could not create deployment: file:/home/heffner/Java/jboss-4.0.5.GA/server/default/deploy/joe.ear/joe.jar/
> org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (org.jboss.ws.WSException: Multiple context root not supported)
> 	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
> 	at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:83)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy29.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy8.deploy(Unknown Source)
> 	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
> 	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
> 	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
> 	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy4.start(Unknown Source)
> 	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
> 	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy5.deploy(Unknown Source)
> 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
> 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
> 	at org.jboss.Main.boot(Main.java:200)
> 	at org.jboss.Main$1.run(Main.java:490)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.ws.WSException: Multiple context root not supported
> 	at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.createJBossWebAppDescriptor(ServiceEndpointGeneratorEJB.java:258)
> 	at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.generatWebDeployment(ServiceEndpointGeneratorEJB.java:71)
> 	at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB3.generateWebDeployment(DeployerInterceptorEJB3.java:127)
> 	at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:49)
> 	at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78)
> 	... 75 more
> Switching back to 1.2.0.SP1 works.
> I'm using onyl Annotations to configure the provided services. Example of one test service:
> @Local
> @WebService
> public interface DatabaseService
> {
>     @WebMethod
>     public String dbmsAlert(@WebParam(name = "alert") String alert, @WebParam(name = "message") String message); 
> }
> @Stateless
> @WebService(endpointInterface = "de.spiegel.joe.service.DatabaseService")
> public class DatabaseServiceImpl implements DatabaseService
> {
>     private static final Logger log = Logger.getLogger(DatabaseServiceImpl.class);
>     @PersistenceContext
>     EntityManager entityManager;
>     
>     public String dbmsAlert(String alert, String message)
>     {
>         log.debug("Received alert '"+alert+"' with message '"+message+"'.");
>         return "OK";
>     }
> }
> What can I do to solve this issue?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list