james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara" <apa...@bago.org>
Subject Re: Switch to Loom 1.0RC3
Date Thu, 08 Sep 2005 08:28:00 GMT
> > I'm not sure I would like to use phoenix-trunk: does any 
> other project 
> > use it?
> Does anyone use LOOM?
> From what Peter Royal told me, I understood that development 
> on LOOM is dead.  And we don't have access to the code.  I'd 
> like to hear from Peter regarding Loom vs Phoenix, but he 
> seemed willing to help us update the container.

Well, LOOM had a release cycle in the last year and we have access to
sourcecode, buglist, feature, documentation, and an 1.0RC3 distribution
For Phoenix we have a repository trunk that does not run james, no feature
list, no documentation and no official distribution.

I Just tested the 2 distributions Peter sent to me today. One runs under the
same conditions of Loom (needed to change the data-sources configuration),
the other one (the one he's using) does not find a package that I've not
been able to find anywhere (java.lang.NoClassDefFoundError:

> And I never proposed that we precipitously dump the Avalon 
> interfaces.  I am suggested that we not add MORE 
> dependencies, and start to incrementally drop the one's we have.

I already explained this: IMHO the change removed avalon specific source
code in favor of avalon specific configuration. BTW this is an useless
discussion: we can deploy our dbcp class by removing/changing the schema.xml
file from the just released cornerstone-datasources-impl-2.1.jar.
This exact problem does exists with both Phoenix-LatestFromPeterRoyal and
Loom-1.0RC3 (1).

Now that I looked to it better phoenix-trunk didn't work for the same exact
issues Loom didn't: simply Loom gave me better error and I found the
problems and fixed them.

Now our codebase is compatible with phoenix-trunk, phoenix-4.0.4 and

Our config.xml is not valid but the important thing is that the code is
Both phoenix-trunk and loom-1.0RC3 should correctly handle the classpath for
the contained application (they add any jar in SAR-INF/lib to the


(1) Just look at this file:

It validates the "data-souces" element only when its class attribute contain
the "org.apache.avalon.excalibur.datasource.JdbcDataSource" line.

<element name="data-source">
<attribute name="name"/>

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message