[
https://issues.jboss.org/browse/JBWS-2535?page=com.atlassian.jira.plugin....
]
Jesse Sweetland commented on JBWS-2535:
---------------------------------------
I'm getting this in EAP 5.1.0. Only one of my EJBs has @SecurityDomain. I've
tried both "JBossWS" and my custom domain, and I get the error in both cases.
The only way to avoid the error is to remove @SecurityDomain entirely.
Multiple security domain check is too overzealous
-------------------------------------------------
Key: JBWS-2535
URL:
https://issues.jboss.org/browse/JBWS-2535
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-integration
Environment: Not sure about components or versions. It's definitely happening
in AS 5.0.0.GA.
Reporter: Galder ZamarreƱo
Assignee: Darran Lofthouse
If you mix up EJB3 SLSBs without security domains and SLSBs with
SecurityDomain("other"), and
you add an EJB3 WS endpoint to the deployment archive, the deployment would fail with an
exception
similar to this:
Caused by: java.lang.IllegalStateException: Multiple security domains not
supported
at
org.jboss.wsf.container.jboss50.deployment.tomcat.SecurityHandlerEJB3.addSecurityDomain(SecurityHandlerEJB3.java:58)
at
org.jboss.wsf.container.jboss50.transport.WebAppGenerator.createJBossWebAppDescriptor(WebAppGenerator.java:268)
at
org.jboss.wsf.container.jboss50.transport.WebAppGenerator.generatWebDeployment(WebAppGenerator.java:101)
at
org.jboss.wsf.container.jboss50.transport.WebAppGenerator.create(WebAppGenerator.java:85)
at
org.jboss.wsf.container.jboss50.transport.EJBHttpTransportManager.createListener(EJBHttpTransportManager.java:78)
at
org.jboss.wsf.framework.deployment.HttpTransportDeploymentAspect.create(HttpTransportDeploymentAspect.java:76)
at
org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.create(DeploymentAspectManagerImpl.java:121)
at
org.jboss.wsf.container.jboss50.BareWSFRuntime.create(BareWSFRuntime.java:61)
at
org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:84)
at
org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:43)
at
org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60)
at
org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:112)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
... 18 more
The validation seems to be a bit too overzealous.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira