Thinking further about this, we have to define carefully how this
relates to the "cocoon:" protocol, because in such a case we have _two_
request paths :
- the protocol-level path, accessible using getRequestURI(),
- the sitemap-level path, accessible using getSitemapURI() (different
from the
efix.
Thoughts ?
Something like that was also my first thought... just hesitated to
propose a change/addition of the Request interface ...since I only need
it inside the sitemap - so I came up with the idea of the environment
module.
Shall we add it to the Request?
Sounds even bett
> -Original Message-
> From: Max Larsson [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 26, 2001 1:18 PM
> To: 'Cocoon Dev'
> Subject: Request interface
>
>
> Hi,
>
> i don't know if it should be the way it is or not,
> but i'd
Hi,
i don't know if it should be the way it is or not,
but i'describe anyway.
As much i understand the Requets interface in
org.apache.cocoon.envirnoment has the same
function like the HttpRequest object from the
Servlet API. If that's true where is the
setCharacterEncoding method from Servlet
