Jess Holle wrote:
Can anyone shed any light on the plans for Tomcat using Jakarta Collections 3.0?
I ask as we currently bundle Jakarta Collections for use in and out of the servlet engine. We wish to use a consistent version throughout. Given that Tomcat bundles Jakarta Collections within its common/lib area, we effectively use whatever Tomcat uses while in the servlet engine in any case. We're therefore at Collections 2.1 as Tomcat is.
Are there plans to move Tomcat to Jakarta Collections 3.0?
It would have been better if either: - 3.0 was backwards compatible with 2.0 :) - it was using different package names
Note that you should be able to override and use collections 2.1 inside a webapp even if collections 3.0 is in common/lib, and hopefully it'll work. If it doesn't, there will be a huge mess, and lots of hate mail ;)
Or vice versa presumably?
If this *should* work, then I can give it a wing, though I've not really sanity checked 3.0 myself -- as we use 2.1 very little and my immediate concern was Tomcat compatibility.
-- Jess Holle
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
