portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Berger <ber...@imn.htwk-leipzig.de>
Subject Re: [jira] Commented: (JS2-376) request parameter encoding problem
Date Tue, 11 Oct 2005 17:12:33 GMT

> It throws an exception because there is no pipeline named "test".
> I objected to taking out this line:
>
>          String targetPipeline = context 
> .getRequestParameter(PortalReservedParameters.PIPELINE);
>
> since it would break any URLs coming from the browser with the 
> pipeline parameter on it. This is currently how Fusion works: the 
> pipeline is passed on the URL, not as a request attribute. 
> Additionally, any existing HTML/Javascript that depends on the 
> pipeline request parameter will be broken. Again, your soluton seems 
> disproportionate in tradeoffs: are you saying that, with your patch, 
> the portal can no longer make use of request parameters? I must be 
> missing something here
>
Ah OK, I see. I didn't know that this is required. So I agree, this 
would really break Fusion and some HTML/Javascript.
Hence we have two possibilities:
- Find a way to invoke setCharacterEncoding() before 
getRequestParameter(PortalReservedParameters.PIPELINE).
- I send you a patch for the other solution I suggested in the JIRA issue.

The first one should be difficult to implement as the CapabilitiesValve 
should do this. Do you have an idea?

Regards, Thorsten


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message