[jboss-jira] [JBoss JIRA] Commented: (JBAS-6060) Tolerate security domain convention in JBoss DD

[Anil Saldhana (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12433146#action_12433146 ] 

Anil Saldhana commented on JBAS-6060:
-------------------------------------

The code location where the change will happen is the AbstractWarDeployment.java and Container.java

> Tolerate security domain convention in JBoss DD
> -----------------------------------------------
>
>                 Key: JBAS-6060
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6060
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB2, Security, Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.CR2
>            Reporter: Anil Saldhana
>            Assignee: Anil Saldhana
>             Fix For: JBossAS-5.0.0.GA
>
>
> The historic expectation in jboss-web.xml and jboss.xml was to specify the security domain with a prefix of "java:/jaas/" .  Example, if an user wants to configure a domain of "test" for a web app, the 
> jboss-web.xml would look like:
> <jboss-web>
>   <security-domain>java:/jaas/test</security-domain>
> </jboss-web>
> The java:/jaas is an internal implementation of JNDI binding by JBoss. There should be no real expectation from the user to follow this syntax.
> EJB3 has already got away from this notion.
> So we should tolerate a domain configuration without context prefix.

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