No, I didn't expect it to hel... But there was a bug with URLs and the includeParams attribute, although I don't think this is the same issue. Do you know if there's an official bug report for the render parameter behaviour?
Nils-H On Thu, Apr 16, 2009 at 8:58 PM, Stephen Turner <stur...@mit.edu> wrote: > On Thu, 16 Apr 2009 14:02:31 -0400, Nils-Helge Garli Hegvik > <nil...@gmail.com> wrote: > >> That does indeed seem a little odd... The portlet framework expects >> these parameters, so I'm not sure there is a way around it. Did you >> try upgrading to 2.1.6? >> >> Nils-H >> > > I do suspect the Oracle portal is at fault - as I mentioned, straight JSR > 168 portlets also cause a problem when using render params in the Oracle > portal. > > I didn't think upgrading to 2.1.6 would help, but I tried anyway and am now > getting a runtime exception: > > 09/04/16 14:41:40 struts2-hello: [id=75664163303,2] WARNING: Could not find > action or result > There is no Action mapped for action name WSRPBaseService. - [unknown > location] > > We are accessing our portlets through WSRP - "WSRPBaseService" is used in > the markup URL. No idea why this is being interpreted as a Struts action > though! > > Steve > > -- > Stephen Turner > Senior Programmer/Analyst - SAIS > MIT IS&T > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
