It doesn’t make any
difference. Just create your JSF app as you would if it were running
stand-alone. MyFacesGenericPortlet and your friendly JSR-168 portlet
container will take care of the rest. Most of the magic is done in the javax.faces.context.ExternalContext.
See the javadoc for details. There have been some reported problems
with multiple JSF portlets in LifeRay, but hopefully it is fixed by now. From: Marcio E Miranda
[mailto:[EMAIL PROTECTED] Hi, How does MyFaces (or JSF for that matter) handle backing
beans in multiple instances of the same portlet? For example, let’s say
that I’ve deployed two instances of MyPortlet in the same page of a
portal. MyPortlet defines a view which has components binded to a backing bean
that must be saved for each portlet instance, because it holds information
specific to that portlet instance (in portlet API terms, it should be stored in
the Portlet session with portlet scope). Does JSF handle portlet scope in the managed bean creation
facility (and in EL)? If not, how would I handle that in JSF? How should I
create the backing bean and how should I reference it using EL? Thanks, |
- RE: Portlet support - multiple instances of a por... Stan Silvert
- RE: Portlet support - multiple instances of ... Marcio E Miranda
- Re: Portlet support - multiple instances of ... Patrick Dalla Bernardina