Hi, Regarding portlets and myfaces integration, I noticed another "detail" that will potentially become a serious headache: the FacesContext instance is kept in the portlet session. So, if I have 10 portlets on a page, I have 10 FacesContext instances per user eating up me server memory. This is unacceptable from a performance perspective. Could Mr. Stan Silvert (stated author of myfacesgenericportlet) explain the design decision? Are there alternatives?
Thanks, Bolerio -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 6:48 PM To: MyFaces Discussion Subject: Re: Portlet examples needed by portlet/MyFaces users I'm sure it's possible. Facelets did it. I use jstl functions in my pages under facelets. On 9/13/06, Iordanov, Borislav (GIC) <[EMAIL PROTECTED]> wrote: > Hi, > > Does anybody know whether it's possible and how to write a customer > variable resolver for the standard implementation of JSTL? That'll solve > another problem with portlets: JSF correctly puts managed beans in a > portlet session (via the external context I guess), but the JSTL EL > looks at the "servlet level" so you can't access JSF managed beans with > JSTL. This has probably been discussed at length and probably there is a > standard solution and probably it'll be dealt with in the upcoming > version of the specs, but in the meantime....? > > Thanks > Bolerio >
