[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1963) Fix the ssladvanced testcase against AS trunk

[jaikiran pai (JIRA)]

     [ https://jira.jboss.org/jira/browse/EJBTHREE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved EJBTHREE-1963.
------------------------------------

    Resolution: Done


Done in r96882.

> Fix  the ssladvanced testcase against AS trunk
> ----------------------------------------------
>
>                 Key: EJBTHREE-1963
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1963
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: testsuite
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> ejb3-ssl-advanced testcase deploys a test config (ejb3-ssl-connector-service.xml) which configures the JaasSecurityDomain:
> <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
>          name="jboss.security:service=JaasSecurityDomain,domain=SSLAdvanced">
>      <!-- This must correlate with the java:/jaas/SSL above -->
>      <constructor>
>         <arg type="java.lang.String" value="SSLAdvanced"/>
>      </constructor>
>      <!-- The location of the keystore
>           resource: loads from the classloaders conf/ is the first classloader -->
>      <attribute name="KeyStoreURL">localhost.keystore</attribute>
>      <attribute name="KeyStorePass">opensource</attribute>
>   </mbean>
> This MBean internally depends on the jboss.security:service=JaasSecurityManager by default. However, this dependency is not explicitly specified. 
> Earlier versions of AS (prior to 6.0 M2) used to configure and deploy the jboss.security:service=JaasSecurityManager service from the JBOSS_HOME/server/< servername>/conf/jboss-service.xml which would guarantee that by the time the ejb3-ssl-connector-service.xml from deploy folder was picked up for deployment, the jboss.security:service=JaasSecurityManager would be available. However, with the recent refactoring of the conf/jboss-service.xml in AS trunk, the legacy services have been moved to server/servername/deploy/legacy-conf-service.xml. With this, it's no longer guaranteed that the jboss.security:service=JaasSecurityManager will be available before the ejb3-ssl-connector-service.xml is deployed. 
> A explicit dependency in the JaasSecurityDomain is what is required:  
> <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
>          name="jboss.security:service=JaasSecurityDomain,domain=SSLAdvanced">
>      ...
> 	<depends>jboss.security:service=JaasSecurityManager</depends>
>   </mbean>

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