All,
It seems to me that the next logical step is to discuss the current
API vs. what it should become. IMHO, David's proposal to construct
Castor using both JCA and JMX is superb. In order to get started
on this, we must first decide what portion(s) of the current API
should be considered the core of Castor JDO and what pieces of the
current API can be broken out into their own modules (e.g. conf,
drivers, oql, etc.). However, I think that the current API could
stand to be broken up (e.g. engine and persist really need to be
split up) into more logical packages. Thomas, Ilia and Ned have
already been discussing this a bit (caching, locking, etc.) but
only a small portion. Let's expand this discussion to include what
should be the Castor JDO core and what should be a module. My
thinking on this stems from the fact that the part of the core will
be an implementation of an MBean server architecture and the modules
can be implemented as MBeans and at least the drivers could be
implemented using JCA.
Again, I may be fired up about nothing, but I certainly like David's
proposal. To me, this modular architecture is truly what has propelled
JBoss to the next level.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
