Scott, > Yes, all VelocityPortlets get their own context. I am going try > using HashMap request attribute "templateMap" keyed by portlet id > to overcome this. I am also going attempt break the template > logic into a single, separate component that can be used by > VelocityPortlets and JspPortlets. That way when changes happen, > the impact on both types of portlets will be more apparent. I
That was my original goal, to create a base TemplatePortlet and TemplatePortletAction, but no time :( Please open up a Bugzilla issue for this. Thanks! BTW: The setTemplate issue is tracked here: http://issues.apache.org/bugzilla/show_bug.cgi?id=16443. > think I am one of those rare exceptions that use both Velocity > AND jsp portlets. I'm using both Velocity and JSP as well. Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
