Thanks for the insight Tim, very interesting, and it makes sense.
However, it doesn't make sense. :P This has never happened to this application running on JBoss 4.0.x in over a year....and never happened when I tested it against Glassfish V1.
Is there a classloader bug in Glassfish V2 that might be causing this?
Both the source code and version of Wicket I'm using remains unchanged in the entire time it has been in production...so I'm very skeptical that this is anything *other* than an issue w/ Glassfish.
[Message sent by forum member 'zambizzi' (zambizzi)]
http://forums.java.net/jive/thread.jspa?messageID=216379