Re: [Wicket-develop] Have we taken the covariant return types way to far?

[Janne Hietamäki]

On 26.7.2006, at 14.11, Matej Knopp wrote: We were hunting a bug with Johan, which turned out to be fact that  AjaxRequestTarget.EncodingResponse is derived from Response instead of  WebResponse. WebRequestCycle.getReponse casts the response to WebResponse, which  means that all responses used in WebRequestCycle have to be  WebResponses. Does this make sense? Does it make sense to have  StringResponse, NullResponse, etc... all derived from WebResponse  instead of Response? I don't think so. I think we should revert the deprecation of  WebRequestCycle#getWebResponse and make getResponse just return Response. Ideas? -Matej I agree. WicketPortletResponse also extends Response, not WebResponse, and I am planning to implement AJAX support to the portlets, so at least there should not be any dependencies to the Web*-stuff. Janne Hietamäki Cemron Ltd http://www.cemron.com/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop