"Quinton McCombs" <[EMAIL PROTECTED]> writes:
>> If this really is a container problem, then we should think
>> about adding a property for the content tool to never encode
>> the jsession id (just as the old 2.2 code did).
>Allowing ContentTool to be configured not to call encodeURL() has fixed
>my problem. I posted a separate message to the dev list with an
>approach to allow configurable tools. Assuming this is approach is
>agreeable to everyone, I will commit the changes.
Good to hear, but we should check if we're simply working around a
container bug or if we just did something "not allowed" by sending all
the URLs through encodeURL. And then document the outcome. IMHO, you
stepped on a bug in your container.
Regards
Henning
>
>> Hm. One more item on my todo list. :-/
>>
>> Regards
>> Henning
>>
>> --
>> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
>> [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
>>
>> Java, perl, Solaris, Linux, xSP Consulting, Web Services
>> freelance consultant -- Jakarta Turbine Development -- hero for hire
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
