> It's not a case of an unknown reference causing the not serializable > exception. I know which object is not serializable and it is the concrete > proxy object created by WebLogic for my remote EJB. I ended up checking if I > was in development mode and then using a transient variable and then using a > another variable which is not transient when the app is running in a > production environment. I was hesitant to simply mark the EJB as transient > in case it caused issues in the production environment. Thanks all for your > replies, they helped confirm that there wasn't a workaround other than > marking it transient.
But there is. You can turn the check off, even for development mode. See IDebugSettings#setSerializeSessionAttributes[1] What you probably want in the end though, is a construct like @SpringBean or just look the bean up right at the moment you need it without holding the reference. Eelco [1] http://wicket.sourceforge.net/apidocs/wicket/settings/IDebugSettings.html ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
