JCA Deployer Related

[anil.saldhana]

I looked around, could not figure out what is parsing the security-domain element in:

<?xml version="1.0" encoding="UTF-8"?>

<connection-factories>
 <no-tx-connection-factory>
 <jndi-name>RunAsIdentityFS</jndi-name>
 <rar-name>jca-securedejb.jar#notxfs.rar</rar-name>
 <connection-definition>org.jboss.test.jca.fs.DirContextFactory</connection
-definition>
 <config-property name="FileSystemRootDir" type="java.lang.String">/tmp/db/
fs_store</config-property>
 <config-property name="Roles" type="java.lang.String">RunAsIdentityRole,Ru
nAsRole2</config-property>
 <security-domain>RunAsIdentityFSRealm</security-domain>
 </no-tx-connection-factory>
</connection-factories>

Because the security-domain is not getting injected to the BaseConnectionManager.

[starksm64]

Its parsed based on the jaxb annotations on the org.jboss.resource.metadata.mcf.SecurityDomainMetaData class. The org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer is the deployer that controls this.

[anil.saldhana]

I am not sure any SecurityDomain is getting created in the BCM. The way the BCM startService() is coded is:

if (securityDomainJndiName != null && jaasSecurityManagerService == null)
 throw new DeploymentException("You must supply both securityDomainJndiName and jaasSecurityManagerService to use container managed security");

if (securityDomainJndiName != null)
 securityDomain = (SubjectSecurityManager) new InitialContext().lookup(SECURITY_MGR_PATH
 + securityDomainJndiName);

So basically there needs to be an injection of securityDomainJndiName. This is not happening at all.

The test case I was peeking at was:

org.jboss.test.jca.test.SecurityContextUnitTestCase

Adrian's rant about the JCA security integration is here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=124525