[ 
https://issues.apache.org/jira/browse/PB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ate Douma resolved PB-13.
-------------------------

    Resolution: Won't Fix

I've completely lost track of this one, sorry.
As far as I know the Liferay "extension" of the Struts Bridge already does 
something like what you asked for, so I guess its not really needed for your 
situation anymore.
And nobody else has ever complained about this problem, so I'm going to close 
this one as "Won't Fix" for now.
If anyone is hit by this problem, please reopen the issue and I'll have a 
second look at it.

> Extra parameters injected into portlet request
> ----------------------------------------------
>
>                 Key: PB-13
>                 URL: https://issues.apache.org/jira/browse/PB-13
>             Project: Portals Bridges
>          Issue Type: Bug
>          Components: struts
>    Affects Versions: 1.0
>            Reporter: James Schopp
>         Assigned To: Ate Douma
>            Priority: Minor
>             Fix For: POST-1.0
>
>
> The extra parameters "_spage", "_sorig", and "_kra" get added to the portlet 
> request  For some applications (IBM WebFacing, for example), these 
> un-expected parameters cause issues. Allthough they may be necessary for the 
> Struts bridge, they should be filtered out by the time the request reaches 
> the actual portlet.
> I have solved this by creating a new RequestWrapper that filters these 
> parameters (configurable in portlet.xml). The wrapper is created (and wrapped 
> around the real request) in my ServletContextProvider.
> Ate, this may be something you consider app-specific, but it's pretty 
> configurable, and there is no overhead if you do not configure any parameters 
> to be filtered. So, it's more flexibility, with no drawbacks (and it get's it 
> out of my code and into yours ;-)
> see: http://support.liferay.com/browse/LEP-529
> thanks, james

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to