It works fine on our target platform (GlassFish). This is due to GF's
environment being different than that of Tomcat. It's a fairly unusual
bug - we've never encountered one before that cratered us on
non-GlassFish containers, while not effecting GlassFish at all. Due to
a class-loading difference, code that was supposed to be for
documentation only (primarily for tools) was being picked up by the
container.
It's not practical to test on every other servlet container out there -
so we don't. Glassfish is the sole platform we do formal testing on.
Given this experience, I'll be taking another look at that as a
possibility, but resources are tight.
It's an open source product - we rely on users to report problems to us
in their environment. If you are interested in volunteering to do
additional testing, we'd welcome any participation you'd like to give.
Jim
On 10/20/09 12:33 PM, webtier_at_javadesktop.org wrote:
> Yes, the current 2.0.1-SNAPSHOT build solves this problem.
> But it's astonishing that such a major problem can come in between RC2 and FCS.
> [Message sent by forum member 'frank_langelage' (frank_at_lafr.de)]
>
> http://forums.java.net/jive/thread.jspa?messageID=368675
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>