Peter Donald wrote:
Anything that plans to run in Tomcat 4.x has a high chance of not working if you include extension entries. Bugs in TCAll of the Merlin, Assembly, Meta, and Configuration project jars use extension declarations and no problems have been encountered with these jars when running Tomcat standalone, or running Tomcat as an embeded web-server within Merlin, or running Merlin embedded within a servlet under Tomcat. So I guess my experience is different to yours.
But this is drifting from the main point - the are incompatible jar files floating around with limited version control. There is next to no documentation on dependencies between jar files. Different containers are using different jar versions. The overall situation sucks and needs to be addressed. If it actually turns out that the particular situations raise issues - then we can deal with that. For me, the priority concerning getting Avalon products into a manageable state is a much higher priority.
Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
