I have never tried to initialize Filter in the field so I don't have such
problem. Here is my code
In the page I have
@Property
@Persist
private Filter filter;
this field is null at the begining, and it is always passed to the
hibernate in order to apply data filtering, if it is null, no need to do
any filtering.
I have a component that is called FilterData
<t:layout.FilterData filter="filter" />
In that component I have
@Parameter
private Filter filter;
@Property
@Persist
private Filter selectedFilter;
The property selectedFilter is used for the display and manipulation by the
component (probably I could live without this), and once all of the fields
are selected and a run button is pressed I execute something like
filter = new Filter(selectedFilter)
For the user that has done this I can see new object been passed, however
if the same page is refreshed by another user (using a different browser,
or even different machine) I can see that it also has the same object in
the filter property.
I will try to clear code a bit and remove selectedFilter if possible and
see if that helps. But all in all I think I got my answer, still if anyone
has any idea why do I see this problem, feel free to shout :)
Thanks
PS removing @Persist from selectedFilter did not help
On Tue, Sep 16, 2014 at 2:56 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Mon, 15 Sep 2014 19:25:21 -0300, Boris Horvat <horvat.z.bo...@gmail.com>
> wrote:
>
> Reading a tapestry documentation I get that page only has one instance,
>> so does this mean that once I place something in the component's parameter
>> it is unable to determine in which session it should be place?
>>
>
> No. Tapestry itself never persists parameter values in the session.
> Parameters are completely independent from the session. In addition,
> Tapestry uses a single page instance for all requests, but the page state
> (non-annotated fields) is actually stored in a per-request (per-thread)
> map, all this done transparently and automatically, so the state of one
> request doesn't affect other requests at all.
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Sincerely
*Boris Horvat*
