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

2006-07-29 Thread Johan Compagner
whiner. alway whining whinging whining..Stop doing that and start coding.On 7/27/06, Igor Vaynberg [EMAIL PROTECTED] wrote:rolled back! happy now?!? all that hard work! -IgorOn 7/27/06, Eelco Hillenius [EMAIL PROTECTED] wrote:Let's remove it then. The advantage was minimal anyway.Eelco On

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

2006-07-28 Thread Igor Vaynberg
rolled back! happy now?!? all that hard work!-IgorOn 7/27/06, Eelco Hillenius [EMAIL PROTECTED] wrote:Let's remove it then. The advantage was minimal anyway.Eelco On 7/26/06, Janne Hietamäki [EMAIL PROTECTED] wrote: On 26.7.2006, at 14.11, Matej Knopp wrote: We were hunting a bug with Johan,

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

2006-07-27 Thread Eelco Hillenius
Let's remove it then. The advantage was minimal anyway. Eelco On 7/26/06, Janne Hietamäki [EMAIL PROTECTED] wrote: 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

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

2006-07-26 Thread Matej Knopp
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.

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

2006-07-26 Thread 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