[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

[weston.price@jboss.com]

Issue:

The old method of deployment used the RAR->MCF (via the OldRARDeployment attribute) dependency to force the MCF to wait for the RAR to be deployed prior to the MCF entering the start/stop lifecycle. Without this explicit dependency I am running into the case where the *-ds.xml file gets parsed and all the MBeans get created prior to the RAR being deployed. 

Assuming that one of the reasons for repository is to remove the requirement to specify the RAR name in the *-ds.xml, jboss.xml or jboss-service.xml file, this would seem to be problematic due to the inherent dependency between them. 

I am not sure the real value of this anyway as you would expect a deployment type of MCF, listener, AdminObject to specify to which RAR it belonged. 

Obviously this is not the only reason for the repository, but I can't quite see how we can get away with getting rid of the RAR names from our deployments. 


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011035#4011035

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011035