Hi
I currently have issues with Trinidad running in a portal environment
(Pluto RI). The documentation for Configurator states that
beginRequest() / endRequest() should be called exactly once for every
physical request. Whereas the javadoc for beginRequest() in
GlobalConfiguratorImpl states that
Felix,
The global configurator is not a typical configurator. In a normal
Portlet 1.0 environment, there is no guarentee that request scope is
preserved between action and render. So yes, the GlobalConfigurator
gets called for each request (action and then render). Under the
covers, it mak
Hi Scott
Makes sense! One question remains though: obviously the
GlobalConfigurator makes sure that general Configurator's
beginRequest()/endRequest() are only called once per physical
request. How do you detect the end of a physical request in
a portal environment? According to the spec the port
By luck.. :) No really, what basically happens is on an action we
assume we always have a new request. When the action ends, we save a
flag to a session scoped object we have which carries our configurator
state. It is then picked up in the subsequent render and removed at the
end of the r
