On Thursday 25 October 2001 12:26, Matt Sergeant wrote: > On Wed, 24 Oct 2001, Paul Kulchenko wrote: > > Messaging > > Authentication/Identification > > Sessions > > Webservices > > Security > > Database Access > > Auditing/Logging > > Exception and Error tracking > > Workflow Management > > Configuration > > Internationalization > > Transactions > > Directory > > Testing > > Deployment > > Documentation > > You forgot: XML. Yes, it fits into lots of the above, but I think it also > requires its own set of APIs (like JAXP).
Definitely. In fact, I think that some frameworks will be more foundation packages, on top of which others will build. Those probably need to happen first. On the foundation side, I'd list: XML (mostly JAXP/PAXP and probably a few helpers) Configuration Logging Exception/Error I18N Testing Documenation Of course, this doesn't mean that we'll have to have all of these complete before the rest can be worked on, but simply that the rest will likely have to a certain extent to be retrofitted to work with these. -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- Lavish spending can be disastrous. Don't buy lavishes for a while.
