[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1339) @Security domain vs. <security-domain>

[Thomas Diesler (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-1339?page=all ]

Thomas Diesler updated JBWS-1339:
---------------------------------

    Fix Version/s: jbossws-2.0.0
                       (was: jbossws-1.2.0)

Deferred to 2.0

Carlo, sais:

<security-domain> is supported in EJB3. The @SecurityDomain should
override the xml, unless metadata-complete is set. But metadata-complete
is not yet implemented.

I'm not sure what happens in other beans if you have <security-domain>
set for your deployment and @SecurityDomain on one of the beans.



> @Security domain vs. <security-domain>
> --------------------------------------
>
>                 Key: JBWS-1339
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1339
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jaxws
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For: jbossws-2.0.0
>
>
> I have a test where my ejb3 SLSB, jsr181 endpoint works only if I use the @SecurityDomain annotation. If I try to define the security-domain in the deployment descriptor I get a 401 http response code.

-- 
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