render method issue..

[Muzakir Khan，修改在11 年前。]

Suppose there are two portlets say Portlet A and Portlet B. now if there is a request for portlet A from web portal, the portlet A’s render method
is invoked. The content is generated for portlet A, and it’s returned to the portlet
container. Even though the render request was made only for portlet A, the portlet container
invokes portlet B’s render method too.. Now my question is, why is that even though the render req was made only for portlet A, the portlet container even invokes portlet B's render method too?.. Is it the drawback or advantage in Portal Technology?..

Thanks
Khan

[Muzakir Khan，修改在11 年前。]

Any body plz help me out to overcome this doubt?..

[David H Nebinger，修改在11 年前。]

Only the action method is called on portlet A.

When rendering the page post-action, the portal will call the render method on all portlets on the page in order to build the aggregated page.

BTW, this is a question from portal development 101. Please, before you get too far, take a Liferay development course or read the Liferay in Action book or something...

[Muzakir Khan，修改在11 年前。]

David H Nebinger:

Only the action method is called on portlet A.

When rendering the page post-action, the portal will call the render method on all portlets on the page in order to build the aggregated page.

BTW, this is a question from portal development 101. Please, before you get too far, take a Liferay development course or read the Liferay in Action book or something...

Thanks David.. Actually I am reading Manning Portlets in Action book.. There I got this doubt, It was not explained why the render method for all portlets is called. Thats why I posted it..

[Manish Yadav，修改在11 年前。]

if you don't want to call render method of portlet B.Then you need to use Ajax .serviceResouce method need to call for ajax call.

[Subhash Shah，修改在11 年前。]

This is part of more refined request handling process of portlets.
It is actually part of Java Portlet Specification 1.0.
It says "Normally, a client request triggered by an action URL translates into one action request and many render requests, one per portlet in the portal page. A client request triggered by a render URL translates into many render requests, one per portlet in the portal page."