Just for the records:
NEVER do that: log4j.rootCategory=info, A1
That will cause every message to be logged twice. I had managed that by
misconfiguring maven resource filtering...
-
http://www.winfonet.eu
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-2-6-Activate-c
Hi guys,
Thanks for the replies. In fact I had some img tags with no src-attribute as
a placeholder for the designers to deliver their content. I replaced them
now with properly styled divs. Although what was strange, they were on
totally different pages. So I could not imagine them being the reas
This is almost always due to a bad URL; the browser gets the
URL, there's no actual file, it ends up invoking the Index page
passing the bad path as activation context.
On Thu, Aug 11, 2011 at 12:42 PM, Thiago H. de Paula Figueiredo
wrote:
> On Thu, 11 Aug 2011 15:44:51 -0300, nillehammer
> wro
On Thu, 11 Aug 2011 15:44:51 -0300, nillehammer
wrote:
Hi List,
Hi!
I suddenly realized that onActivate allways get's
called twice.
Have you checked what context values does onActivate() get in these two
requests?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5
Are you instantiating (injecting) the page somewhere? onActive is
called called once when required, you have to tell more about your
case if you want reasonable answers.
Kalle
On Thu, Aug 11, 2011 at 11:44 AM, nillehammer
wrote:
> Hi List,
>
> I've never really used onActivate so I did not care
Hi List,
I've never really used onActivate so I did not care about how often it would
be called... up to today. I have a single onActivate(EventContext context)
and corresponding onPassivate in my page class and use the context to load
som data from the db. I suddenly realized that onActivate allw
