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
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 m
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)
pa
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"
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