Hi Michael, Thanks for the suggestion! But, I think <portlet:namespace/> is intended more for avoiding intra-page html/javascript naming conflicts, rather than for the bug I'm experiencing. Besides, I'm installing portlets that I didn't write, so I have no control over how their code was written and whether or not they used the <portlet:namespace/> to prefix every single one of their render parameters.
- Frank > -----Original Message----- > From: Michael Kearns [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 03:53 AM > To: Jetspeed Users List > Subject: Re: SEVERE ERROR: RenderRequest Parameters > > > Frank Villarreal wrote: > > >I'm not sure if this has been identified in JIRA or not ... but > I've noticed > >this error goes back to the Jetspeed 2 release candidate days ... > > > >Whenever there are at least 2 portlets from the same portlet application > >sharing a single PSML page, RenderRequest parameters submitted by one > >portlet instance are visible to BOTH portlets (even though they are > >completely different portlets) on each request. However, if the both > >portlets happen to be from DIFFERENT portlet-apps, then the > error appears to > >not occur. I suppose this is some type of namespacing issue in the > >underlying architecture ... not sure if this is a Jetspeed or > Pluto issue. > >Any ideas? This, at least for me is a show stopper b/c I have > many portlets > >I'd like to display side-by-side and am unable to do due to this error. > >Kind of defeats the purpose of using a portal in the first place ... > > > >- Frank > > > > > > I'm guessing this is why the <portlet:namespace/> JSP tag exists. > > Everything (variables, functions, etc.) in every portlet we develop, has > this prefix, to ensure it never happens. > If it is actually incorrect behaviour, you'll then need functionality to > allow portlets to share the render request parameters. > > Just ensure you have safe namespacing throughout (which is always a good > idea for web/XML development) and there'll be no problems. > > Michael. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > The information contained in this e-mail is confidential and is intended only for the use of the individual or entity to which it is addressed. Dissemination, distribution, copying or use of this e-mail is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete the message from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
