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
[EMAIL PROTECTED] 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
begin:vcard
fn:Brian Hawkins
n:Hawkins;Brian
org:;Development
adr:suite A122;;34 E 1700 S;Provo;UT;84606;USA
email;internet:[EMAIL PROTECTED]
title:Software Engineer
tel;work:801-705-9306
x-mozilla-html:TRUE
url:http://www.lingotek.com
version:2.1
end:vcard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
