Ok. Let me put this a different way:
I have a working implementation of the ManagedConnectionFactoryParser and the
ManagedConnectionFactoryDeployer. The repository is also set up and working to contain all
the metadata that is being constructed on the deployment chain.
I also have a working implementation where I can construct the MCF/Pool/Binding etc. Right
now all I do is simply emulate what the XSL deployer does in setting the appropriate MBean
attributes that allows the
| org.jboss.resource.connectionmanager.RARDeployment
|
to start, create the ManagedConnectionFactory, set the properties and associate the MCF
with the ResourceAdapter (if it supports it). The Pool, CM ,Binding all other MBeans that
may arbitrarily appear in the *-ds.xml file follow in the same manner.
It's at this point I am not clear on your vision for doing this differently. The whole
'guess the RAR' thing to me seems to be unnecessarily complicated and I am not
quite sure of the point being that a JCA deployment MCF, ActivationSpec, AdminObject
should always know to what RAR it belongs.
If something above doesn't appeal to you (as I am sure it doesn't) don't
hesitate letting me know in that warm and loving way of yours ;-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013693#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...