I see, we are actually talking about "state in page" vs "state in
component" approaches.
>> the component encapsulates the knowledge about specific
>> url parameters that it needs
> So given the above this appears to me to be paradoxical, if you are going to
> encapsulate the url parameters then
"
Sent: Tuesday, 22 September, 2009 12:01:14 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re: Accessing page context from a component
Chakra words reminds me of the interesting idea for components to have
their independent activation context. That page is not aware of.
In this case th
Chakra words reminds me of the interesting idea for components to have
their independent activation context. That page is not aware of.
In this case the component encapsulates the knowledge about specific
url parameters that it needs. And can be reused on different pages
without altering them. For
Otho is exactly right here. Each piece of Tapestry has its purpose, and
pages act as a bridge between the client and the components within the page.
On Mon, Sep 14, 2009 at 4:13 AM, Otho wrote:
> I wouldn't couple a component so tightly to a specific page. If you need to
> pass certain bits of
I wouldn't couple a component so tightly to a specific page. If you need to
pass certain bits of information you can also use component parameters from
within the page.
2009/9/14 chakra
>
> thanks for the responses.
> Is there any plan in future releases of tapestry, to add support for
> onActiv
thanks for the responses.
Is there any plan in future releases of tapestry, to add support for
onActivate method in components also,to get the page context?
That will make life much easier.
Chakra
--
View this message in context:
http://www.nabble.com/Accessing-page-context-from-a-component-t
If the context needs to be shared, it needs to be exposed to the rest of the
environment in some way.
One option is for the page to implement an interface; components get get the
page (from ComponentResources) and cast it to the interface to obtain the
desired information.
Another option is a per-
What about injecting ComponentEventLinkEncoder and Request to the component and
call #decodePageRenderRequest(request) to get PageRenderRequestParameters.
It contains the activationContext.
DH
http://www.gaonline.com.cn
- Original Message -
From: "chakra"
To:
Sent: Sunday, September 1
