It looks as though this is some subtlety (or brokenness) to GlassFish
and Toplink. If I deploy my Wicket app as a module of a Java
Enterprise package, it all works as expected.
It's a simple workaround for now until I find out if it's a bug, or if
I'm just not getting my Glassfish config correct.
Basically, using NetBeans, I create a new "Enterprise Application",
add my Wicket app as a Java EE module, then deploy. Et voila!
In any case, I can move on for the moment. ;)
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
