cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Hawkins <>
Subject Re: HttpServletRequest?
Date Wed, 22 Mar 2006 16:27:08 GMT
In thinking about this more I think the best solution all around is to 
have the cocoon Request interface inherit from the HttpServletRequest 
interface.  Then it could be passed around and used in any servlet.


Brian Hawkins wrote:
> This brings up a good question.  Why does cocoon feel the need to wrap 
> every object?  The cocoon Request interface is (as far as I can tell) 
> identical to the HttpServletRequest interface.  From the code the only 
> difference is that is wraps other objects like the session.  All this 
> seems to do is frustrate developers who have to inter operate with 
> other servlets running in the same container.
> Fernando,  I think the solution for both of us is to hack the 
> HttpRequest object and provide a getHttpServletReuqest method.
> Brian
> wrote:
>> In a component, I need to call a third-party method which takes a 
>> HttpServletRequest as a parameter.
>> In this component, I have access to a cocoon Request.
>> How can I do to get to an HttpServletRequest? The method I want to 
>> call needs to look at the headers and source IP address.
>> Thanks
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message