wish Jesse to fix the bug in T5.
Jun Tsai
2007/6/26, Jesse Kuhnert <[EMAIL PROTECTED]>:
I don't know if this helps or not, but I got generics working in a very
limited way with 4.1.x in that I do all the type lookup work
manually...(this probably won't work for this use case but thought I'd
th
I don't know if this helps or not, but I got generics working in a very
limited way with 4.1.x in that I do all the type lookup work
manually...(this probably won't work for this use case but thought I'd throw
it out just in case it does, even this breaks down in many places)
http://svn.apache.or
Francois Armand wrote:
Actually, it's not really an acceptable solution, but the sole
workaround I know (if somebody as another idea, I would be glad to use
it).
Well, this sentence is not true.
You may ask users to implement a "factory" interface for Class they
intend to use as parameter type
Howard Lewis Ship wrote:
There's an existing bug for this. I'm not sure how fixable it's going
to be; welcome to the implementation nitty gritty of generic types and
type erasure. Just cause you don't see the typecasts doesn't mean the
compiler has put them there.
Here's a challenge: what if th
There's an existing bug for this. I'm not sure how fixable it's going
to be; welcome to the implementation nitty gritty of generic types and
type erasure. Just cause you don't see the typecasts doesn't mean the
compiler has put them there.
Here's a challenge: what if there was a createWidget()
I have a Widget base entity extended by several concrete product
entities. I have
public class EditWidgetPage
{
...
@Persist
public Long _someWidgetId;
public T _someWidget;
// normal setters / getters
void onActivate (long id)
{
_someWidgetId = id;
_someWidget = _dao.get (id);
