> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Monday, November 03, 2003 8:32 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: One Panel with 3 JSP Portlets
> 
> 
> Hi,
> Stefan
> what you say is right, and it is the only solution that I 
> have thought,but it is valid for small portlet application, 
> for a large or complex portlet it becomes a problem I think. 
> thanks for your participation Holger Dewes, what you have 
> written it is a lot interesting. My action Example JspPortletActionB
> 
> public class JspPortletActionB extends JspPortletAction  {
> 
>     public void buildNormalContext(Portlet portlet, RunData rundata)
>     {
>     }
>     public void doDetailsb(RunData data, Portlet portlet) 
> throws Exception
>     {
>         setTemplate(data, "ContactB.jsp");
>     }
> 
> }
> 
> change template persistently for all subsequent requests 
> until it is changed again,is what i want :-) 
> I use setTemplate, can you make a code example of the other 
> technique? thanks to all for the participation into the discussion.

try setTemplate(date, "ContactB.jsp", true)

>From the javadoc (PortletAction.setTemplate(RunData data, String
template, boolean persistent)):

This method is used when you want to short circuit an Action and change
the template that will be executed next. If the <code>persistent</code>
attribute is set to <i>true</i> the template value is stored in the
portlet's session state and will be used until a new value has been set,
either within portlet session or within the context.  Regardless of the
value of <code>persistent</code>, the context will ALWAYS have the
correct "template" attribute set within.

HTH

-- 
Holger Dewes


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to