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 is perthread scope. > 2) Contribute a filter to the ComponentActionRequestHandler pipeline. > The filter can capture the event context and store it in your service. > 3) In your PersistentFieldStrategy, inject the context-storing service > and read the context. > > You might simplify #1 to just store the piece of data you need from the > context. > > The approach is similar if you need page activation context, but > you'll need to contribute a similar filter into the > PageRenderRequestHandler pipeline as well. > > On Jan 17, 2008 12:13 PM, Ted Steen <[EMAIL PROTECTED]> wrote: > > 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 into my PersistentFieldStrategy in order to be > > able to read the context? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- /ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
