So this will be new behavior for JBoss application server 6 – JBoss 4 and 5 call start followed by the setResourceAdapter calls on the MCF and ActivationSpec? ironjacamar-1.0.0.Beta3 (or a subsequent beta) will become part of JBoss AS 6 or will only a standalone container be supported for version 1.6 of the connector architecture?
This has never been an issue with any application server – I admit I've never tried Geronimo, but WebLogic, GlassFish, WebSphere, and the Oracle Application Server call start followed by the setResourceAdapter calls. Just getting started with the WebSphere 8 beta, so maybe it too performs as ironjacamar.
So this will be new behavior for JBoss application server 6 – JBoss 4 and 5 call start() followed by the setResourceAdapter calls on the MCF and ActivationSpec? ironjacamar-1.0.0.Beta3 (or a subsequent beta) will become part of JBoss AS 6 or will only a standalone container be supported for version 1.6 of the connector architecture?
This has never been an issue with any application server – I admit I've never tried Geronimo, but WebLogic, GlassFish, WebSphere, and the Oracle Application Server call start followed by the setResourceAdapter calls. Just getting started with the WebSphere 8 beta, so maybe it too performs as ironjacamar.
Again thanks for your time.