Investigate org.jboss.test.jca.test.SecurityContextUnitTestCase

This is for HEAD.

The org.jboss.test.jca.test.SecurityContextUnitTestCase is failing in HEAD for the following reason:

There is a calleridentity-ds.xml that is deployed as part of a jar. This ds.xml file contains a set of Datasource definitions with security domain names that are injected by a DynamicLoginConfig service that is defined at the end of the ds.xml file.

================================================================================
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:587)
at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:521)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:330)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:578)
=================================================================================

Basically when the jca service starts, it is trying to authenticate and the configured security domains are not yet installed
(because the Dynamic login config service has not started). This is my guess.

Please verify the behaviors in Branch_4_0 and HEAD.