Re: Problem with assignment of variables between pages
Hello Jesse, the problem is a bit harder to track. All of my test cases (with tons of debug output) worked out as the should. The problem as it seems is that under some circumstances one jsession is able to access the (persistent) variables of another jsessions instance of the same page (or maybe also a different page). The problem mostly occurs after some exceptions were thrown and maybe a hibernate session was left in a questionable state, but i'm not 100% sure if it really has to do with the hibernate session itself. As soon as i find another (hopefully reproducable) appearance of this behavior i'll try to track it again. Regards, Patrick This may have been the case with a previous 4.1.2-SNAPSHOT version that was doing some ~things~ with cglib and properties but I doubt it... If your properties aren't persistent there is no magic happening, they just get set on the object. Perhaps you are doing this in some kind of page loading method like validate() or similar? Even with persistent properties the object is first handed off to the persistent store changes manager impl and then just set on the page object, so there's no valid reason I can think of where this would happen as you've described it. I'd add some breakpoints to your code and run them in any of the standard ide debuggers to find out definitively what is happening if it were me. They leave 0 room for doubt in these situations. On 2/27/07, Patrick Klein <[EMAIL PROTECTED]> wrote: Hi! cache is not disabled. Regards, Patrick > Are you disabling the cache ? > > On 2/27/07, Patrick Klein <[EMAIL PROTECTED]> wrote: >> >> Hallo! >> >> I'm hoping I'm not completely OT with this problem here... >> >> We are using setters and getters to pass over objects between pages, >> like (in pseudo-java) >> >> page a: >> (PageB) page = (PageB) cycle.getPage("PageB"); >> page.setVar(obj); >> [...] >> cycle.activate(page); >> >> page b: >> Obj var = getVar(); >> if(var != null) { >> [...] >> } >> [...] >> public abstract Obj getVar(); >> public abstract void setVar(Obj var); >> >> The problem which is driving us up the walls is that in some cases, the >> transition seems to get messed up, as a not-null object is handed over, >> but on the receiving side this object is null... >> An additional problem is that this behavior seems to be not valid for >> all http-sessions handled by tomcat, some work as they should. >> >> We are using Tap 4.1.2 (SNAPSHOT from 16.02.2007), Tomcat 5.5.17 (and >> 5.5.20) and Hibernate 3.2.1ga with java 1.5.11SE. >> >> Did anyone here encounter a similar problem and if yes, give me a hint >> of where to look or how to fix it? >> >> Regards, >> Patrick Klein >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with assignment of variables between pages
This may have been the case with a previous 4.1.2-SNAPSHOT version that was doing some ~things~ with cglib and properties but I doubt it... If your properties aren't persistent there is no magic happening, they just get set on the object. Perhaps you are doing this in some kind of page loading method like validate() or similar? Even with persistent properties the object is first handed off to the persistent store changes manager impl and then just set on the page object, so there's no valid reason I can think of where this would happen as you've described it. I'd add some breakpoints to your code and run them in any of the standard ide debuggers to find out definitively what is happening if it were me. They leave 0 room for doubt in these situations. On 2/27/07, Patrick Klein <[EMAIL PROTECTED]> wrote: Hi! cache is not disabled. Regards, Patrick > Are you disabling the cache ? > > On 2/27/07, Patrick Klein <[EMAIL PROTECTED]> wrote: >> >> Hallo! >> >> I'm hoping I'm not completely OT with this problem here... >> >> We are using setters and getters to pass over objects between pages, >> like (in pseudo-java) >> >> page a: >> (PageB) page = (PageB) cycle.getPage("PageB"); >> page.setVar(obj); >> [...] >> cycle.activate(page); >> >> page b: >> Obj var = getVar(); >> if(var != null) { >> [...] >> } >> [...] >> public abstract Obj getVar(); >> public abstract void setVar(Obj var); >> >> The problem which is driving us up the walls is that in some cases, the >> transition seems to get messed up, as a not-null object is handed over, >> but on the receiving side this object is null... >> An additional problem is that this behavior seems to be not valid for >> all http-sessions handled by tomcat, some work as they should. >> >> We are using Tap 4.1.2 (SNAPSHOT from 16.02.2007), Tomcat 5.5.17 (and >> 5.5.20) and Hibernate 3.2.1ga with java 1.5.11SE. >> >> Did anyone here encounter a similar problem and if yes, give me a hint >> of where to look or how to fix it? >> >> Regards, >> Patrick Klein >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with assignment of variables between pages
Hi! cache is not disabled. Regards, Patrick Are you disabling the cache ? On 2/27/07, Patrick Klein <[EMAIL PROTECTED]> wrote: Hallo! I'm hoping I'm not completely OT with this problem here... We are using setters and getters to pass over objects between pages, like (in pseudo-java) page a: (PageB) page = (PageB) cycle.getPage("PageB"); page.setVar(obj); [...] cycle.activate(page); page b: Obj var = getVar(); if(var != null) { [...] } [...] public abstract Obj getVar(); public abstract void setVar(Obj var); The problem which is driving us up the walls is that in some cases, the transition seems to get messed up, as a not-null object is handed over, but on the receiving side this object is null... An additional problem is that this behavior seems to be not valid for all http-sessions handled by tomcat, some work as they should. We are using Tap 4.1.2 (SNAPSHOT from 16.02.2007), Tomcat 5.5.17 (and 5.5.20) and Hibernate 3.2.1ga with java 1.5.11SE. Did anyone here encounter a similar problem and if yes, give me a hint of where to look or how to fix it? Regards, Patrick Klein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with assignment of variables between pages
Are you disabling the cache ? On 2/27/07, Patrick Klein <[EMAIL PROTECTED]> wrote: Hallo! I'm hoping I'm not completely OT with this problem here... We are using setters and getters to pass over objects between pages, like (in pseudo-java) page a: (PageB) page = (PageB) cycle.getPage("PageB"); page.setVar(obj); [...] cycle.activate(page); page b: Obj var = getVar(); if(var != null) { [...] } [...] public abstract Obj getVar(); public abstract void setVar(Obj var); The problem which is driving us up the walls is that in some cases, the transition seems to get messed up, as a not-null object is handed over, but on the receiving side this object is null... An additional problem is that this behavior seems to be not valid for all http-sessions handled by tomcat, some work as they should. We are using Tap 4.1.2 (SNAPSHOT from 16.02.2007), Tomcat 5.5.17 (and 5.5.20) and Hibernate 3.2.1ga with java 1.5.11SE. Did anyone here encounter a similar problem and if yes, give me a hint of where to look or how to fix it? Regards, Patrick Klein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with assignment of variables between pages
Hallo! I'm hoping I'm not completely OT with this problem here... We are using setters and getters to pass over objects between pages, like (in pseudo-java) page a: (PageB) page = (PageB) cycle.getPage("PageB"); page.setVar(obj); [...] cycle.activate(page); page b: Obj var = getVar(); if(var != null) { [...] } [...] public abstract Obj getVar(); public abstract void setVar(Obj var); The problem which is driving us up the walls is that in some cases, the transition seems to get messed up, as a not-null object is handed over, but on the receiving side this object is null... An additional problem is that this behavior seems to be not valid for all http-sessions handled by tomcat, some work as they should. We are using Tap 4.1.2 (SNAPSHOT from 16.02.2007), Tomcat 5.5.17 (and 5.5.20) and Hibernate 3.2.1ga with java 1.5.11SE. Did anyone here encounter a similar problem and if yes, give me a hint of where to look or how to fix it? Regards, Patrick Klein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]