I guess I look at it differently. What we requires is a request object and a response object. In jsp, the page context acts as both.

I'm not sure how all controllers and view can't comply with that?

Would you rather introduce a TilesRequest and TilesResponse object?

David

Antonio Petrelli wrote:
2007/2/23, David H. DeWolf <[EMAIL PROTECTED]>:
Instead of passing retrieving the request and response from the
pageContext and passing them through, I would use the pageContext as the
request and response and let the (pluggable) jsp factory recognize it
and create it's context using it instead of the req/res pair.


Hmm... I don't like the idea of using the concept of request/response
to the PageContext.
Moreover, we should provide a way of considering all possible
combinations of controller (I mean servlet, portlet, etc.) and view
(JSP, FreeMarker...) technologies, and the single factory
(TilesContextFactory) can only help with the most common case.

Antonio

Reply via email to