Next step in my quest for full trinidad and portlet compatibility was PPR: I've done the following:
- tweaked trinidad to send some additional parameters with each partial request - tweaked my portlet-rendering code to include the portlet-prefix (in the session/application-map) as one of these additional parameters (retrieving the portlet-prefix is still kind of interesting code, I'll have to bring this to maturity, but currently, I ownly rely on the servlet- and portlet-API) - tweaked the trinidad partial submit routine to post these additional parameters to a different action then the one mentioned in the form - behind this action, have a servlet listening for all incoming requests - the servlet wraps request/session/context and uses the portlet-prefix to access attributes in the session/application map, so the servlet knows how to access the corresponding portlet parameters - the servlet sets the UIViewRoot onto the FacesContext so that the UIViewRoot is available - the servlet then executes a full lifecycle This all works pretty nicely, until we get to the point of someone calling url-encoding methods while the rendering in the servlet happens. And this is where I'm at now. Without being in the portlet container, I of course have no way of deriving a portlet-URL. So I strongly suspect I'm stuck for good now, and I need to restart with better ideas. Anyone having some? regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
