Hi Aaron, I read the posted JIRA issue (http://issues.apache.org/jira/browse/JS2-605), I believe my problem is the exact one described .. however, I think it's a really, really bad idea to rely on the incorrect behaviour established by this "feature/bug". Sure, it works great when you're linking between PSML pages and want to pass some parameters to a single portlet-page ... but think about when you have "multiple" portlets on that PSML page that are dependant on like-named variables. You can get some pretty unpredicable results when there are "unexpected" request variables/values coming through in a request! I mean this bug really breaks the spec badly ... almost making it impossible to easily plug-in third party portlets without a lot of headaches ... as I'm finding out. From reading his JIRA comments, sounds like Ate is already aware of this.
Ate:: Any idea or update on how you are going to make this behaviour "configurable"? - Frank > -----Original Message----- > From: Aaron Evans [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 24, 2007 12:33 PM > To: Jetspeed Users List > Subject: Re: SEVERE ERROR: RenderRequest Parameters > > > Hmmm, interesting... > > Note that if you append parameter name value pairs to the query string > of the URL for a jetspeed PSML URL, then you get the same behaviour. > I guess that makes sense in a way... > > This is a "feature" (as Ate mentions in that bug report) that I > exploit quite frequently with my application. > > -aaron > > On 1/24/07, Frank Villarreal <[EMAIL PROTECTED]> wrote: > > Ate, > > > > I ran some more tests (not yet on the latest trunk), but I > thought it might > > be useful and explain why you haven't been able to replicate > the error ... > > > > Only parameters that have NOT been encoded using the PortletURL > class are > > duplicated across portlet instances. So for example, if you > have an html > > form page that contains 50 fields that you are not able to encode using > > PortletURL, then when the form is submitted, every portlet in the same > > application on the same PSML page will also see those > parameters in their > > next doView request ... > > > > - Frank > > > > > -----Original Message----- > > > From: Ate Douma [mailto:[EMAIL PROTECTED] > > > > > > I've just tested with a 2.1-dev trunk snapshot of beginning this > > > month and can't reproduce the problem, using 2 portlets of the > > > same portlet applications on the > > > same page.> > > > > > > > > > > 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] > > > > > > --------------------------------------------------------------------- > 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]
