Sorry,
the excerpt from the log missed the interesting info part:
the source causes an exception:
(leaving out any secondary exception messages)
....
Caused by: java.net.MalformedURLException: Malformed URI in block source
Illegal character in query at index 40:
servlet:/page/research/search?modeinfo=a b
at
org.apache.cocoon.servletservice.ServletConnection.<init>(ServletConnection.java:83)
at
org.apache.cocoon.servletservice.components.ServletSource.<init>(ServletSource.java:70)
at
org.apache.cocoon.servletservice.components.ServletSourceFactory.getSource(ServletSourceFactory.java:71)
at
org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:152)
at
org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:182)
at
org.apache.cocoon.template.script.DefaultScriptManager.resolveTemplate(DefaultScriptManager.java:103)
Nevertheless,
I assume the problem is put up quote before entering the sitemap. As it is
already visible there.
Probably there is something along the get() method for request parameters that
changed (as a side effect from SSF?) (wild guess)?
Rainer
Rainer Pruy schrieb:
> Hallo,
> again hitting real world...
>
> I'trying to get some request parameters to their final destination (a local
> generator)
> however I always end up with decoded ones.
>
> The whole topic starts out from a js function handling a form and at some
> point is calling (showing the effective resulting string here)
>
> cocoon.redirectTo("search?modeinfo=a+b", {});
>
> (The '+' resulting from using URLEncode("a b"))
>
> This redirect call ends up with a pipeline resulting in the following
> generator call:
>
> <map:generate
> src="servlet:/page/research/{1}?modeinfo={raw-request-param:modeinfo}"
> type="jx"/>
>
> In the (debug) log this results in the following line:
>
> btpool0-1 DEBUG components.ServletSourceFactory - Creating source object for
> servlet:/page/research/search?modeinfo=a b
>
> (Thus it looks like somehow "raw-request-param" does not return undecoded
> parameters?)
> When using "request-param" module the result is the very same.
>
> As this is with cocoon 2.2 (1.0.0-RC1) did this change form 2.1.x?
> (where I used such pattern sucessfully in the past (this was with some 2.1.7
> if I remember correctly))
>
> Any ideas?
>
> Thanks for any help
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Rainer Pruy
Geschäftsführer
Acrys Consult GmbH & Co. KG
Untermainkai 29-30, D-60329 Frankfurt
Tel: +49-69-244506-0 - Fax: +49-69-244506-50
Web: http://www.acrys.com - Email: [EMAIL PROTECTED]
Handelsregister: Frankfurt am Main, HRA 31151
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
