Quinton McCombs wrote:
I see. What would you suggest for as a container solution for Turbine
to be able to load Avalon components? Although we use commons-logging
for our logging, it is using log4j as the actual logging solution. This
is why I need to be able to use log4j.
Ah, I see too :D

It kind-of depends on relative release schedules I guess. As soon as fortress is out, I'd recommend fortress. Since we're trying to do lots of things over here at the same time (still setting up our top-level project stuff, and wanting to d oa synched release of various avalon components, and wanting "Quality Assurance" on fortress), the release is pretty much getting delayed more and more.

Still, I'm a bit reluctant to do an intermediate ECM release, as it is not our future, and we'll be recommending upgrading to fortess later.

There's also plexus of course, which could be a good choice, but I haven't been tracking their work very closely anymore so I can't tell.

cheers,

- Leo



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to