I was doing some testing with ironjacamar-1.0.0.Beta3 and I noticed that ResourceAdapter.start is called after a ManagedConnectionFactory instance is configured and after the called to ManagedConnectionFactory.setResourceAdapter.
Shouldn't ResourceAdapter.start be called before an MCF is configured (at least before setResourceAdapter is called)? In the Connector Architecture specification it states that the start method should be called before any other object belonging to the resource adapter is used. This is from section 5.3.5
The application server must call the start method on the ResourceAdapter JavaBean (in order to create a functional resource adapter instance), before accessing other methods on the ResourceAdapter JavaBean instance or before using other objects that belong to the same resource adapter instance.
I was doing some testing with ironjacamar-1.0.0.Beta3 and I noticed that ResourceAdapter.start is called after a ManagedConnectionFactory instance is configured and after the called to ManagedConnectionFactory.setResourceAdapter.
Shouldn't ResourceAdapter.start be called before an MCF is configured (at least before setResourceAdapter is called)? In the connector architecture specification it states that the start method should be called before any other object belonging to the resource adapter is used. This is from section 5.3.5:
The application server must call the start method on the ResourceAdapter JavaBean (in order to create a functional resource adapter instance), before accessing other methods on the ResourceAdapter JavaBean instance or before using other objects that belong to the same resource adapter instance.