Thanks for pointing this out, however, I think it's a related but different issue. I did not notice any classloader problems in my case, and anyway, we deploy our entire application (web pages, EJBs and entity classes) in a single WAR.
Regards, Harald -----Ursprüngliche Nachricht----- Von: kbs [mailto:kbs_kulbhus...@yahoo.com] Gesendet: Freitag, 9. Juli 2010 09:17 An: users@wicket.apache.org Betreff: Re: AW: Serialization of injected EJBs I am not sure if this is related but AFAIR we faced a similar problem with GlassFish V2.1 and determined the root cause of this to https://issues.apache.org/jira/browse/WICKET-2416 The exception stack trace may be different in V3 so I am not sure if it is same issue. Regards, Kulbhushan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
