|
The strange thing is that it works in a
web application. Who is responsible for saving the state of
a component? I’m tracing the flow from the Lifecycle and realized that it
goes like
Lifecycle.render()->ViewHandler.render()->externalContext.dispatch()->PortletRequestDispatcher.include().
Up to this point no save state is called, so I guess the tag lib will save the
state (or call the state manager). Also, does the extension filter have
anything to do with state management? I’m not using it in the portlet
application (but I’m using it in the web application), since servlet
filters are not supported in portlets. Regards. From: Stan Silvert
[mailto:[EMAIL PROTECTED] I don’t see how this is
possible. The same LifeCycleImpl.response() is called whether in a
portlet or a servlet. The MyFacesGenericPortlet doesn’t have
anything to do with calling StateHolder objects. Maybe you have StateHolder A that wraps
StateHolder B. StateHolder A forgets to call StateHolderB.saveState() ? From: Marcio E Miranda
[mailto:[EMAIL PROTECTED] Forgot to mention that I’m using
MyFacesGenericPortlet as the JSF portlet implementation. Regards From: Marcio E Miranda
[mailto:[EMAIL PROTECTED] Hi, We have some custom JSF components in our project that save
and restore state. The state management works fine if the components are used
in a web application, but if they are used inside a portlet, the save and
restore methods are never called. I’ve tried using the client and server
methods. Is component state management enabled inside a portlet? Thanks. ______________________ |
- RE: Component state management inside portlets Marcio E Miranda
- RE: Component state management inside portlets Stan Silvert
