cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: Request
Date Mon, 13 May 2002 15:19:37 GMT
Vadim Gritsenko wrote:

>>From: Artur Bialecki [mailto:artur@digitalfairway.com]
>>
>>
>>>-----Original Message-----
>>>From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
>>>Sent: Monday, May 13, 2002 10:31 AM
>>>To: cocoon-dev@xml.apache.org
>>>Subject: RE: Request
>>>
>>>
>>>>From: Artur Bialecki [mailto:artur@digitalfairway.com]
>>>>
>>>>>-----Original Message-----
>>>>>From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
>>>>>
>>>>>>From: Artur Bialecki [mailto:artur@digitalfairway.com]
>>>>>>
>>>>>>
>>>>>>It would be nice if there was an easy way to convert
>>>>>>HttpServletRequest to HttpRequest, HttpServletResponse to
>>>>>>HttpResponse, etc.
>>>>>>
>>>>>>Right now I can't see any easy way of doing this.
>>>>>>Maybe new constructors or static conversion methods
>>>>>>that do this would be very useful.
>>>>>>
>>>>>>What do you think ?
>>>>>>
>>>>>Why this would be needed?
>>>>>
>>>>If you start a new cocoon project and you're _not_ using
>>>>other libraries that already _extend/return_ HttpServletRequest
>>>>and others than you probably don't need it.
>>>>
>>>>But, if you have some request/response/cookie processing
>>>>libraries which were used in Cocoon1 or your JSP site
>>>>and you're moving to Cocoon2 and want to use these
>>>>from XSP, etc. you either have to rewire (If you can)
>>>>your libraries to use cocoon's Request, Response, etc.
>>>>or preform the conversion in some easy way. Since the
>>>>first option may not allways be feasable.
>>>>
>>>Do you know that Http* objects *are* *already* available in Cocoon?
>>>Hence my question: why do you need wrappers if you can use original
>>>Http* objects?
>>>
>>I know that you can
>>
>objectModel.get(HttpEnvironment.HTTP_REQUEST_OBJECT)
>
>>but that only solves passing requests/responses/cookies into library
>>methods. But when methods return/extend HttpServletRequest (etc.) I
>>
>can't
>
>>do the following in my XSPs or logicsheets:
>><xsp:logic>
>>  request = new SuperRequest(request);
>>  //or
>>  request = UberHttpLib.getUberRequest(request);
>></xsp:logic>
>>
>>if the SuperRequest extends HttpServletRequest
>>or the getUberRequest returns HttpServletRequest.
>>
>
>Ok, that's good enough reason to have wrapper/converter.
>

There's already such an adapter in DeliImpl, along with a ServletContext 
adapter. We should move them to environment.http so they have a better 
visibility.

Sylvain

-- 
Sylvain Wallez
  Anyware Technologies                  Apache Cocoon
  http://www.anyware-tech.com           mailto:sylvain@apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message