Hi Michael,
By using the tag <portlet:namespace />, you can bypass the problem, but
I agree with Frank, it is a severe bug because the specification JSR-168
is very clear in this aspect:
PLT.11.1.1 Request Parameters
...
A portlet must not see any parameter targeted to other portlets.
...
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]
