If anyone has an experience to use the IronJacamar embedded with AS7 naming component, could you share your naming.xml please? Or as7 naming cannot be started in standalone like jnpserver?
jnpserver depends on old jboss-logging-spi 2.x which conflicts with other components using jboss-logging 3.x, so I'm now trying that.
Thanks for your comment Jesper,
It sounds like you should use the Arquillian configuration of AS7 instead. You will have access to deploying resource adapters and datasources in that environment too. Check the AS7 test suite for usage.
Hmm, maybe. SwitchYard has AS7 integration test phase and we're using Arquillian on it. What I'm thinking now is for the unit testcases of SwitchYard JCA gateway, and investigating whether the IronJacamar embedded is good for that purpose or not. So, if Arquillian/AS7 is better for this purpose, I may need to cook up the MockResourceAdapter, MockTransactionManager and etc for the unit testcases, and postpone some other testcases to the AS7 integration phase. Do you recommend the Arquillian/AS7 for my case?
IronJacamar/Embedded is targeted against resource adapter development - e.g. the end result is a .rar. The environment helps with testing that it will work once deployed to a JCA container; IronJacamar/Standalone, AS7, whatever.
If you have more than just a .rar you will need the AS7 Arquillian environment. But why would you need to Mock stuff ? Maybe take a look at how HornetQ's resource adapter is integrated / tested in AS7.
But why would you need to Mock stuff ?
SwitchYard is providing the test toolkit for the SwitchYard application developpers, and I want to provide the unit test support for the applications which use JCA gateway without actual connection to the EIS. So it will need at least MockResourceAdapter even if the IronJacamar embedded was appropriate for that purpose.
We already have AS7 integration test using Arquillian on another phase, and I will have testcases for the JCA gateway with AS7 and HornetQ ResourceAdapter via Arquillian on that phase.