On Tue, 24 Jul 2001, David Jencks wrote:
> When Toby Allsop was developing the jca stuff in jbosscx he often wrote
> that all resource access would be moved to the jca framework soon ( I hope
> I'm not misquoting).
>
> I think this means rabbit hole, and I think this is a good idea.
>
> I think the time is NOW. Lets get everyone experimenting with rabbit hole
> to use the jca framework to see if there are bugs in it!
>
> Is anyone working on this? I can if asked.
>
> Aside from identifying and removing unused classes, what needs to be done?
> Is a written migration guide enough or do we need some kind of automatic
> jcml transformation?
One simple task would be to rewrite the JDBC and XA MBeans so that
instead of instantiating DB pools themselves, they simply create a RA
deployment using the standard DB RARs. That way no configs would need to
change - we'd achieve the same result (i.e. a live DB pool) in the DB
MBeans by interfacing with the JCA deployer instead of directly with the
pooling code.
Now, for a new configuration you could just use the JCA stuff
directly, so this would essentailly be a "backward compatibility" feature.
On the other hand, the old DB pool configuration is still somewhat clearer
than the RAR configuration, which requires a lot of JCML blocks to be
configured.
In reply to Bill's reply, the standard DB RARs *do* use the
JBossPool code, so the code doesn't disappear. The MBeans just don't
interact with it directly.
Aaron
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
