It's cool, I got someone on the Glassfish forums to confirm that it's most
likely an issue w/ the app server. I fell back to a prior version and the
problem has disappeared completely.
Thanks for the help, guys!
Johan Compagner wrote:
>
> igor is right these are just 2 classloaders
> if you k
igor is right these are just 2 classloaders
if you know the place where it does goes wrong now and then
output/log the 2 classloaders: log.debug(usersession.getClass
().getClassLoader())
johan
On 5/10/07, V. Jenks <[EMAIL PROTECTED]> wrote:
Thanks for the insight Igor, very interesting, and
i dont use glassfish. just pointing out what can cause the problem.
-igor
On 5/10/07, V. Jenks <[EMAIL PROTECTED]> wrote:
Thanks for the insight Igor, 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
Thanks for the insight Igor, 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 yearand never happened when
I tested it against Glassfish V1.
Any idea what might be causing this?
Both the sou
On 5/10/07, V. Jenks <[EMAIL PROTECTED]> wrote:
"com.myapp.abcommerce.ui.admin.UserSession cannot be cast to
com.myapp.abcommerce.ui.admin.UserSession"
...oh REALLY now?
this is a classloader problem. UserSession loaded by classloader A cannot be
cast to UserSession loaded by classloader B
I'm attempting to test against the latest Glassfish app server (V2 b41,
a.k.a. Beta 2) and there seems to be an issue with wicket that didn't arise
when I had tested it in earlier versions of Glassfish. I realize the app
server may be to blame but that may not be entirely true, I'm just trying to
