Frank Villarreal wrote:
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"?
Have you considered the standard way to encode render parameters with
action or render URLs
<portlet:actionURL var="nodeLink" >
<portlet:param name="node" value="${name}" />
</portlet:actionURL>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
