Actually, I haven't studied avalon much, I believe they both were developed for a similar purpose, at the same time (past 3 years). I've concentrated on easing development, with configurability and reuse, as well as scalability with configurable pooling. Building many business systems from the ground up, I just got tired of the repetitive issues involved in development, deployment, and scalability. Since the code was all the same at heart, I finally open sourced it to my clients, and made it public not long ago...so I don't have to keep rewriting it for each new client. ;)

So, to answer your question the best I can (some of this is speculation), I believe the iverticalleap projects take it a bit further down the business side of things, where avalon remains a core infrastructure.

BTW- In CVS you should find some code under the project java.biz.profile which is an example, using the java.xmldb and java.core projects for stuff like Person management, of course it uses Xindice.

Everyone here might be interested in the java.xmldb project. It contains a high/low UID generator, and DataSourceBroker with configurable pooling for xmldb connections!

-Kevin Ross

Gianugo Rabellino wrote:

Kevin Ross wrote:

Oh yeah, did I mention, the iverticalleap java.core project already does this for you (@see http://www.iverticalleap.com/java.core/index.html)? There isn't much documentation, but the project has been in production use as is for a while, and the codebase has been around for years. At least take a look at my configuration doc with particular attention to services, it my give you some ideas (@see http://www.iverticalleap.com/java.core/configuration.html). Of course, this project was built with business systems in mind, not server systems, but I think the issues we are attempting to tackle (modularity) are common.


Will definitely take a look at it, looks very interesting. How does it relate to Avalon?

Ciao,





Reply via email to