RE: Ajax and Portlets

[Papaioannou, Todd]

The lifecycle is part of it, but the rest of the problem is the action/render url abstraction

that your portal uses. Let's say you have a basic command link in one of your pages. That's

a pretty simple example, with what should be a simple form action url. However, once

you've run that through the portal rendering phase, it might look like:

 

http://pulse:8080/c/portal/layout?p_l_id=PRI.15.1&p_p_id=MyMessages_WAR_MyMessagesPortlet_INSTANCE_WzEa&p_p_action=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_pos=0&p_p_col_count=3&_MyMessages_WAR_MyMessagesPortlet_INSTANCE_WzEa_org.apache.myfaces.portlet.MyFacesGenericPortlet.VIEW_ID=%2Fview.xhtml&#p_MyMessages_WAR_MyMessagesPortlet_INSTANCE_WzEa
If you come in the "front door" you won't be able to get JUST your portlet content
from the portal, because the portal will wrap that content with the rest of the content. I.e.
the rest of the portlets.
 
If you want to backdoor the portal and return the JSF content yourself, you need to be able to 
convert your urls to the portal format. That's problematic, since each portal will do it differently.
 
Hence, I use DWR to back door to my portlet and just do DOM updates locally.
It adds complexity to the design, but achieves what I need.
 
Todd

---

From: Rogerio Pereira [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 05, 2006 4:09 AM
To: Papaioannou, Todd
Subject: Re: Ajax and Portlets

2006/8/4, Papaioannou, Todd <[EMAIL PROTECTED]>:

Not with anything that includes commandButtons or commandLinks. With

Liferay at least, the portal caching gets in the way. Going a back door

route to get the page from JSF breaks because you can't then ensure

that the links are compliant to the portal's url structure. Well, without

a lot of really portal specific code.

I was thinking here and you is right, the main problem with Portlets and MyFaces Tomahawk/Sandbox components are related with Portlet x JSF Lifecycle (Servlet/Portlet Request/Response mentioned before), some of these issues will be only solved on Portlet 2.0 where this one will provide resouce serving interface for portlet and portlet filter.

--
Yours truly (Atenciosamente),

Rogério