2009/3/5 Nathan Bubna <[email protected]>:
> I looked through most of the code and don't see the problem, assuming
> that ImportAttributeModel.getImportedAttributes(...) works as
> expected. I've got some other things to do at the moment, but i'll
> try to find some time to install and run it myself today. I've been
> meaning to get to that anyway.
I think I got it.
Tiles2Tool is request scoped. Now, through the use of Tiles2Tool, a
page is "included".
In the first page is created a ChainedContext (call it "1"), in the
included page a new ChainedContext is created ("2").
The problem is that Tiles2Tool is created and initialized when the
request starts, and its velocity context is the one assigned in "1",
since it is there that the Tiles2Tool is firstly used.
But when used in the included page, it still refers to "1", though it
should refer to "2".
Is there a way to solve this problem?
Thanks
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
