JBoss ASF - ServerSessionPool

[adrian.brock]

So the ServerSessionPool api changed again.

This time to IOCise the transaction manager for Bill's embedded ejb3.

This has been ported across jboss-4.0 and jboss-3.2.x branches so we are now
back in sync.

That's at least 3 days of this year I've wasted synching branches and checking
code modifications not ported properly.

[adrian.brock]

The real purpose of this thread is to discuss "fixing" this api once and for all.

Issues:
* It will be going away once every JMS vendor supports JCA1.5
* The api has about four levels of indirection and still doesn't yet let you plugin
virtually any new behaviour without replacing the whole lot.
* Any change to add new behaviour requires breaking this api (although it is NOT
a public api anyway!)
* There are still some fixes outstanding.

I'll deal with each individually on separate threads.

[adrian.brock]

Issues:
* It will be going away once every JMS vendor supports JCA1.5

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73573

* The api has about four levels of indirection and still doesn't yet let you plugin
virtually any new behaviour without replacing the whole lot.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73574

* Any change to add new behaviour requires breaking this api (although it is NOT
a public api anyway!)

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73575

* There are still some fixes outstanding.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73576