May 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-700) Update documentation for dealing with attachments

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-700?page=all ] Heiko Braun updated JBWS-700: ----------------------------- Affects Version/s: jbossws-2.0.0 > Update documentation for dealing with attachments > ------------------------------------------------- > > Key: JBWS-700 > URL: http://jira.jboss.com/jira/browse/JBWS-700 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: productization > Affects Versions: jbossws-2.0.0 > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-2.x > > > Align with it's dependencies -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1565) Document swaRef usage with JAX-WS endpoints

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1565?page=all ] Heiko Braun updated JBWS-1565: ------------------------------ Description: @XmlAttachmentRef (was: @XmlAttachmentPart) > Document swaRef usage with JAX-WS endpoints > ------------------------------------------- > > Key: JBWS-1565 > URL: http://jira.jboss.com/jira/browse/JBWS-1565 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-2.0.1 > > > @XmlAttachmentRef -- 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

16 years, 11 months

1
0
0 / 0

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

by Arjan van Bentem (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1622?page=comments#action_12362858 ] Arjan van Bentem commented on JBWS-1622: ---------------------------------------- At http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046101#4046101 Heiko Braun explained the cause of this (and it seems to me that this answered Rick's questions, but he was not the reporter of this issue). Arjan. > 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 > Assigned To: Darran Lofthouse > > 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1609) Address in WSDL - Port value is -1 when server is requested with default port 80

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1609?page=comments#action_12362830 ] Magesh Kumar B commented on JBWS-1609: -------------------------------------- Completed and is available in branch braches\jbossws-2.0 > Address in WSDL - Port value is -1 when server is requested with default port 80 > -------------------------------------------------------------------------------- > > Key: JBWS-1609 > URL: http://jira.jboss.com/jira/browse/JBWS-1609 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-1.2.0.SP1 > Environment: JBoss AS 4.0.5 running in port 80 and SSL port 443 > Reporter: Magesh Kumar B > Assigned To: Magesh Kumar B > Fix For: jbossws-2.0.0 > > Time Spent: 1 day, 5 hours > Remaining Estimate: 0 minutes > > When the server is running on default ports 80 the Webservices list and the WSDL URL shows the port as "-1" and when the SSL port 443 is used the Webservice list shows as "-1" and the WSDL URL shows as "http://jbossws.undefined.host:80" -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1651) Merge To Trunk - JBWS-1647 - Text Node Preservation For Messages Sent Across The Wire

by Darran Lofthouse (JIRA)

Merge To Trunk - JBWS-1647 - Text Node Preservation For Messages Sent Across The Wire ------------------------------------------------------------------------------------- Key: JBWS-1651 URL: http://jira.jboss.com/jira/browse/JBWS-1651 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.1.0 -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1650) UnsupportedOperationException when using Java 6

by Chris Laprun (JIRA)

UnsupportedOperationException when using Java 6 ----------------------------------------------- Key: JBWS-1650 URL: http://jira.jboss.com/jira/browse/JBWS-1650 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Chris Laprun 2007-05-05 00:52:57,542 ERROR [org.jboss.ws.jaxrpc.CallImpl] Call invocation failed with unkown Exception java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424) at org.jboss.ws.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:65) at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:115) at org.jboss.ws.binding.soap.SOAP11BindingProvider.createMessage(SOAP11BindingProvider.java:59) at org.jboss.ws.binding.soap.SOAPBindingProvider.bindRequestMessage(SOAPBindingProvider.java:89) at org.jboss.ws.binding.soap.SOAP11BindingProvider.bindRequestMessage(SOAP11BindingProvider.java:65) at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:645) at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:404) at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:148) -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBWS-1585) WSDLFilePublisher throws a java.security.AccessControlException: access denied

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1585?page=comments#action_12362346 ] Heiko Braun commented on JBWS-1585: ----------------------------------- I would like to include your suggested patch, but unfortunately i cannot reproduce the bug. Could you provide further details on this? I.e. the policy files in places? > WSDLFilePublisher throws a java.security.AccessControlException: access denied > ------------------------------------------------------------------------------- > > Key: JBWS-1585 > URL: http://jira.jboss.com/jira/browse/JBWS-1585 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxws > Environment: jbossws-1.0.4.GA > Reporter: Roland Räz > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > When the security manager is enabled the class org.jboss.ws.server.WSDLFilePublisher causes an AccessControlException because it uses the file constructor with the given url. > e.g. > java.security.AccessControlException: access denied > (java.io.FilePermission file:/var/opt/jboss4/jbossiv/current/temp/jboss/temp/jbossws/Sample181Service64187.wsdl delete) > Using an URI and the correct constructor resolves this issue: > ... > if (wsdlFile.startsWith(config.getServerTempDir().toURL().toExternalForm())) > { > URI uri = new URI(wsdlFile); > File file = new File(uri); > file.delete(); > } > ... -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1613) Provide an integration layer for RI tools

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1613?page=all ] Heiko Braun updated JBWS-1613: ------------------------------ Fix Version/s: jbossws-2.0.0 (was: jbossws-2.0.1) > Provide an integration layer for RI tools > ----------------------------------------- > > Key: JBWS-1613 > URL: http://jira.jboss.com/jira/browse/JBWS-1613 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > We should have a binary dependency on the JAXWS RI toolset instead of maintaining a fork -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1613) Provide an integration layer for RI tools

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1613?page=comments#action_12362345 ] Heiko Braun commented on JBWS-1613: ----------------------------------- It's in branch 2.0 and needs to be added to trunk. > Provide an integration layer for RI tools > ----------------------------------------- > > Key: JBWS-1613 > URL: http://jira.jboss.com/jira/browse/JBWS-1613 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Thomas Diesler > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > We should have a binary dependency on the JAXWS RI toolset instead of maintaining a fork -- 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

16 years, 11 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1622?page=comments#action_12362340 ] Thomas Diesler commented on JBWS-1622: -------------------------------------- We need to have a comprehesive test case for jaxws that is equivalent to the JBWS-165 test case. > 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 > Assigned To: Darran Lofthouse > > 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

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2007