Hi Christine, I'm not an expert as a portlet developer, but what I supposed when I saw this restriction is that a portlet is just a piece of a page, so you can have the same porlet (with different namespace!) two times in the same page. With the last spec (jsr-286) you can pass parameters in more natural way.
In my experience, when you are programing with portlets you have to be always aware that: - you can have the portlet more than one time on a page, so be careful with you javascript variables. Use namespace. - one portlet page is the composition of one or more portlets, so be careful with the state of every "piece" of the page when you leave that page. Anyway, there are some workarounds to do it :=) s2o http://s2o-bcn.blogspot.com/ 2009/9/28 Christine <christ...@christine.nl> > Christine wrote: > >> This may be a jsp question more than a jetspeed question. >> Suppose I create a link, like so: >> Name: <a href="?name=<%=p.getFirstName() %>"><%=p.getFirstName() %> >> > Right. > I found this (JS2-605): > "Query string parameters should not (by default) be provided to portlets to > be compliant to JSR 168 spec requirements" > > and this: > <js:metadata > name="merge.portal.parameters.with.portlet.parameters">true</js:metadata> > <js:metadata > name="merge.portal.parameters.before.portlet.parameters">true</js:metadata> > > My first question is, why should url parameters not be passed to a portlet, > as the spec requires? I can imagine url parameters that override portlet > parameters can be a risk, but otherwise, what's the rationale behind not > passing them? > Second, I suggest to make this issue more clear in the documentation or in > the tutorial or in the faq. > > :-) > > > dagdag > Christine > > > > -- > dagdag is just a two-character rotation of byebye. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org > For additional commands, e-mail: jetspeed-user-h...@portals.apache.org > >
