Re: AjaxFormSubmitBehavior causes serialization issues inside onBeforeRender()

to only the ones on ChildPanel.class Thanks, Allgo -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AjaxFormSubmitBehavior-causes-serialization-issues-inside-onBeforeRender-tp2328509p2329578.html Sent from the Wicket - User mailing list archive at Nabble.com

AjaxFormSubmitBehavior causes serialization issues inside onBeforeRender()

) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) However when I add the AjaxFormSubmitBehaviour to individual form components and comment out the onBeforeRender it works fine without any errors.. any clue guys? Cheers, Allgo -- View this message in context: http://apache-wicket

Extract DNS web-url from Wicket request

be intelligent enough to load different CSS files based on which url was tried. Please help and oblige. Thanks in advance! Allgo -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Extract-DNS-web-url-from-Wicket-request-tp2068948p2068948.html Sent from the Wicket - User

Re: Extract DNS web-url from Wicket request

Got the solution.. log.info(x-forwarded-host -+getWebRequestCycle().getWebRequest().getHttpServletRequest().getHeader(x-forwarded-host)); if(getWebRequestCycle().getWebRequest().getHttpServletRequest().getHeader(x-forwarded-host).equals(my-server-one)){

Re: Wicket session not threadsafe?

Hi, The wicket version is 1.3. Sorry should have mentioned that. As such the User A, after he logs on is getting assigned the Account object of User B. And after soem logs we can see that User B had logged on a while before. Hence that Accoutn object was definitely fetched a whiel before. I did

Re: Wicket session not threadsafe?

1.3.0-beta3 actually. Copied it from the Manifest file Martijn Dashorst wrote: 1.3.0? Martijn On Fri, Jan 8, 2010 at 1:12 PM, allgo soumya_...@yahoo.co.in wrote: Hi, The wicket version is 1.3. Sorry should have mentioned that. As such the User A, after he logs on is getting

Re: Wicket session not threadsafe?

implementation caching and returning the wrong object as well. Steve On 08/01/2010, at 11:21 PM, allgo wrote: 1.3.0-beta3 actually. Copied it from the Manifest file Martijn Dashorst wrote: 1.3.0? Martijn On Fri, Jan 8, 2010 at 1:12 PM, allgo soumya_...@yahoo.co.in wrote: Hi

Re: Wicket session not threadsafe?

. Martijn On Fri, Jan 8, 2010 at 1:21 PM, allgo soumya_...@yahoo.co.in wrote: 1.3.0-beta3 actually. Copied it from the Manifest file Martijn Dashorst wrote: 1.3.0? Martijn On Fri, Jan 8, 2010 at 1:12 PM, allgo soumya_...@yahoo.co.in wrote: Hi, The wicket version is 1.3. Sorry should have

RE: Wicket session not threadsafe?

Hi Berin, No the users are all from different companies and no way there woudl be caching of their side. User A belongs to a client X say working in New York , while User B may be of client Y working in texas. It doesnt happen in test environment. but then that is not a multi-user environment

Re: Wicket session not threadsafe?

, Martijn Dashorst martijn.dasho...@gmail.com wrote: There has been a session leak somewhere in 1.3 iirc. This has to do with the thread locals that store Session, RequestCycle and Application during a request not being removed correctly. Martijn On Fri, Jan 8, 2010 at 2:38 PM, allgo soumya_