Hi!
Aaron Mulder wrote:
> Now I'm really confused - I thought all your changes were
> backwards-compatible. Can't you still use the old syntax if you want to?
> I agree that you could work around by using the DataSourceImpl instead,
> but I'm wondering what is actually broken...
The old syntax will work, but it is not compatible with the new startup
process. There is an important order in the startup:
Init phase:
1 Start naming
Start phase:
2 Start Tx-manager (->bind in JNDI)
3 Start DataSource (->bind in JNDI, and lookup Tx-Manager lazily)
Because the current implementation does the lookup in the constructor
the order will be: 1,3,2. I.e. you will try to look up the Tx-mgr before
it has been started and bound into JNDI.
Here's what you need to do:
* Move startup code from constructor to startService().
* Do Tx-manager lookup lazily, in case the Tx-manager is not started
before the DataSource
This is of course only temporary. Once JMX 1.0 is finalized we will make
use of the relationship service to make sure that the proper order in
startup is maintained. If the standard JMX-relationship service is not
enough for our purposes we can easily create this ourselves.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
