How much is/isn't working with your new stuff? I suggest that if many
things are working, you tag the current cvs and then commit. I don't know
what exactly you are working on, but if there are problems exposed in
non-core stuff you might get people to redesign problem areas rather than
applying "quick fixes".
I'm somewhat biased, I have a bunch of connector/pool changes, mostly
involving moving all connector related stuff to connector from pool, and
improving lots of attribute names, however this is going to conflict at
least a little with your stuff since many of these are
ServiceMBeanSupports. I'll hold off on this a little longer if you commit
soon ;-)
What is your migration strategy? Are you going to continue to support
jboss.jcml files? Are you thinking of a migration script type thing? Are
you thinking we will just supply a working jboss with the new stuff and
some instructions on how to migrate and let people sort things out for
themselves? To me this is very relevant because if we eliminate jboss.jcml
there is no reason to have XADataSourceLoader at all... migration can
happen via a script (xsl?) or instructions. If we support jboss.jcml files
we should include XADataSourceLoader but perhaps in a deprecated.jar and
deprecated module.
thanks
david jencks
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
