Kalle Korhonen wrote:
Just FYI for those interested; I made the initial implementation of my
conversation-within-page concept available as an independent Trails module:
trails-conversations (for T5). More information at
http://markmail.org/message/42mxcp3ioiv5tdug#query:conversations%20in%20trail
persistent fields respectivley. I also used the LinkFactory and the
>> LinkFactoryListener to add
>> the conversation id transparently to every link.
>>
>> g,
>> kris
>>
>>
>>
>>
>>
>> Kalle Korhonen
>> 16.01.2009 00:1
estry users"
An
Tapestry users
Kopie
Thema
Re: T5: Reading context before persistent fields are read
Hey Kristian,
yeah I ended up with decorators as well. Did your implementation get any
further than experimental stage? If it's available somewhere, I'd gladly
take a look to
itte antworten an
> "Tapestry users"
>
>
> An
> Tapestry users
> Kopie
> ted.st...@gmail.com
> Thema
> Re: T5: Reading context before persistent fields are read
>
>
>
>
>
>
> Hey Ted,
>
> I happened to run into the same exact problem you
One proper solution to this is to add a decorator to handle() operations of
PageRenderRequestHandler and/or ComponentEventRequestHandler that sticks the
required parameters from the activation context somewhere, for example to a
request attribute to keep it simple, to make it available to your cust
add
the conversation id transparently to every link.
g,
kris
Kalle Korhonen
16.01.2009 00:19
Bitte antworten an
"Tapestry users"
An
Tapestry users
Kopie
ted.st...@gmail.com
Thema
Re: T5: Reading context before persistent fields are read
Hey Ted,
I happened to run int
Hey Ted,
I happened to run into the same exact problem you were having while trying
to get my custom conversational PersistentFieldStrategy implemented. Did you
manage the solve the problem (reading values from activation context before
gathering persistent fields) in any satisfactory way?
Kalle
Hmm, i must have been very tired when i tested this yesterday.
It doesnt work. The ComponentActionRequestFilter is handled after the
persistent fields are gathered. So my activation context variable that
I need when gathering persistent fields is not set before I gather the
fields.
I have tried to
The pipelines and chains of command make it easy to "slip in" specific logic.
OH, an alternative to defining a service to contain the data is to
just write it as a Request attribute. I've used that approach for
handling a few awkward cases.
On Jan 17, 2008 5:56 PM, Ted Steen <[EMAIL PROTECTED]>
Yep, that did it.
Thanks!
2008/1/18, Howard Lewis Ship <[EMAIL PROTECTED]>:
> If you mean the event context (as opposed to the page activation
> context), then ...
>
> The path of least resistance is:
>
> 1) Define a service with a simple read/write property to store the
> context. Make sure this
If you mean the event context (as opposed to the page activation
context), then ...
The path of least resistance is:
1) Define a service with a simple read/write property to store the
context. Make sure this is perthread scope.
2) Contribute a filter to the ComponentActionRequestHandler pipeline
I need to hook in somewhere between where the context is available and
the persistent fields are read.
I need to read a context variable just before my
PersistentFieldStrategy tries to read from the session, as I need a
value from the context when reading from the session.
What should I inject int
12 matches
Mail list logo
