Hi Mark.
The "initial-value" attribute is poorly named.
What it does is initialize your page property when the page
is being *returned* to the pool, so that a page pulled from
the pool has this "initial" property value.
Of course, to facilitate the above, when a page is first
constructed it must be initialized. That's why you're seeing
two invocations: on construction and on return to the pool.
I suggest you carefully read this entire section:
http://jakarta.apache.org/tapestry/UsersGuide/state.html#state.page-properties
And the FAQ "Where do I "initialize" values for a page?":
http://wiki.apache.org/tapestry/MoreFrequentlyAskedQuestions
I'm still using T3, not 4, and I use the PageRenderListener approach:
public void pageBeginRender(PageEvent event)
{
// initialize properties etc
if (!event.getRequestCycle().isRewinding())
{
if (getXXX() == null)
{
...
setXXX(...);
}
}
}
Cheers,
Nick.
Mark wrote:
Hi Ron,
it sounds like this would work, but isn't this just a workaround for
something that really should not happen this way in the first place?
Thanks,
MARK
...
<property
name="roomList">ognl:administrationService.getAllRooms()</property>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
