Scott, Either I didn't think about doing it this way OR it didn't work (I don't remember now but most likely I didn't think about it). Have you tried using your method? It seems that it should work though...
Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ > -----Original Message----- > From: Weaver, Scott [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 06, 2003 12:29 PM > To: 'Jetspeed Developers List' > Subject: Question about JspAction > > > Why was setTemplate(RunData data, String template) deprecated and > public void setTemplate(RunData data, Portlet portlet, String template) > added? The same functionality could have been achieved like this > with out deprecating the existing method signature and adding a new one: > > public void setTemplate(RunData data, String template) > { > Portlet portlet = (Portlet) data.getRequest().getAttribute("portlet"); > if(template != null) > { > PortletSessionState.setAttribute(portlet, data, > JspPortlet.TEMPLATE, > template); > } > else > { > PortletSessionState.clearAttribute(portlet, data, > JspPortlet.TEMPLATE); > } > > } > > The Portlet is ALWAYS placed in the request by the > JspPortlet.getContent() prior ActionLoader.exec(). Is there > something I am missing here that is blatantly obvious? Is there > a chance that JspAction.setTemplate() is invoked prior to > JspPortlet.getContent()? > > Thanks, > Scott > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
