On 11/3/06, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hello everyone,
I'm almost done implementing a custom wrapper for the life cycle which
should allow us to replace a large part of the functionality of our
filter (the other part being handled by FacesContext wrappers). I did
have one question
Oh yeah, and I'm moving wrapping of servlet objects out of the filters
and into the ExternalContext. That does not mean we can't wrap them in
filters as well, but everytime we do, those filters will not run in a
portal.
Scott
Scott O'Bryan wrote:
Two questions then:
1) Being that these
On 11/3/06, Scott O'Bryan [EMAIL PROTECTED] wrote:
Two questions then:
1) Being that these won't work in a portal environment, should we move
these to be executed elsewhere (like my custom lifecycle object) and
change the API to be more container agnostic (ie. using the
ExternalContext)?
On 11/3/06, Scott O'Bryan [EMAIL PROTECTED] wrote:
Then I guess the final question is, is it important if these don't run
in the portal.
I mean if we can't change the API to be container agnostic and ordering
is important, I'm forced to use the Lifecycle/ExternalContext approach
for Portlets
