[
https://issues.apache.org/jira/browse/PLUTO-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved PLUTO-568.
-----------------------------
Resolution: Fixed
I've solved this by now only excluding attributes starting with
"javax.servlet." as those are really reserved for the underlying servlet
container itself.
Namespacing other attribute names *should* not cause side-effects.
Note: this is only a change specific to Pluto Portal Driver, not the portlet
container (which does not concern itself with this functionality).
> Request attributes with javax not getting namespaced and hence colliding
> ------------------------------------------------------------------------
>
> Key: PLUTO-568
> URL: https://issues.apache.org/jira/browse/PLUTO-568
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Affects Versions: 2.0.0
> Reporter: Michael Freedman
> Assignee: Ate Douma
> Fix For: 2.0.1
>
>
> PortletRequestContextImpl doesn't encode/decode attributes whose names start
> with java. or javax. with the portlet instance namespace/prefix. The JSF
> portlet bridge has defined specific request attributes (that begin with
> javax.) that are per instance based. What is the rationale for not encoding
> all request attributes so they are managed on a per portlet instance basis?
> At a minimum we need a fix that allows some/the bridge's attributes to be
> properly encoded so that collisions on the same page don't occur.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
