Yes all of those should work for all deployments.
Actually, let me expand on the last post.
It will basically allow you to have a <teiid> subsystem with your configuration, and then bridge that into the resource adapter services that you need...
HornetQ will be an example of that.
Thanks Jesper and Jason.
Yes, the manifest mechanism is best fit for me.
Jesper, I do not think I want deploy as the shared library. Teiid sub-system as itself does not really need resource adapter services. The Teiid deployment artifacts need access to them. Also user can deploy their own too. I think what you have through standard rar deployer may just work fine. The test example gave me starting point for XML for connection-factory.