« Return to Thread: users, please give us your opinion: what is your take on generics with Wicket

Re: users, please give us your opinion: what is your take on generics with Wicket

by igor.vaynberg :: Rate this Message:

Reply to Author | View in Thread

i think we should have qualified this rfi with a requirement that
responders use 1.4 on a non-trivial project...these things only become
apparent from real-world day-to-day usage. anything else is pretty
much speculation.

-igor

On Tue, Jun 3, 2008 at 10:31 PM, Eelco Hillenius
<eelco.hillenius@...> wrote:

> On Tue, Jun 3, 2008 at 8:54 PM, Mike Comb <mcomb@...> wrote:
>> Well, in our case it would almost never be:
>>
>> MyComponent<MyModel> mycom = new MyComponent<MyModel>();
>>
>> We don't have many of our own models, we use CompoundPropertyModel pretty
>> much exclusively (wrapping DAOs or javabeans).  So the verbosity doesn't
>> benefit us much.  Also, the vast majority of our components don't have a
>> model.  We generally have a page containing one or more forms with a
>> CompoundPropModel on each form.  Having generics (particularly if they are
>> just something like <Void>) on every other object in the page is messy and
>> confusing in my mind.
>
> Yep.
>
>> Telling people to use suppress annotations is not a good solution either, we
>> want those warnings for other things in our code (Collections, etc).
>
> Yep.
>
> Eelco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

 « Return to Thread: users, please give us your opinion: what is your take on generics with Wicket