I have added a comment there concerning the behaviour for literal
bindings. But I dont have permission to change the affected version.
Thanks Lance, you're correct of course.
Michael, as this is still relevant to you, could you please update the
"Affects Version/s:" field of your JIRA issue (TAP5-1213) accordingly?
Am 13.05.2014 11:38, schrieb Lance Java:
No, there is no way to access the generic type, this information is
lost
during the compilation process.
That's not actually correct. Lets consider the following class:
public class MyClass {
private List<Foo> foos;
public List<Bar> getBars() {
...
}
public void doStuffWithBaz() {
List<Baz> bazs = new ArrayList<Baz>();
...
}
}
In this example, the ONLY generic that will be lost after compilation
(due
to type erasure) is Baz. Both Foo and Bar ARE available at runtime.
@see
http://docs.oracle.com/javase/7/docs/api/java/lang/reflect/Method.html#getGenericReturnType()
http://docs.oracle.com/javase/7/docs/api/java/lang/reflect/Field.html#getGenericType()
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
--
Mit freundlichen Grüßen / Kind regards
Michael Wyraz
evermind GmbH
Schorlemmerstraße 1
04155 Leipzig
Tel.: +49 (0)341-25 39 66 - 0
Fax: +49 (0)341-25 39 66 - 1
Funk: +49 (0)177-73 00 00 3
E-Mail: michael.wy...@evermind.de
HRB: 21586
Amtsgericht Leipzig
Geschäftsführer:
Christoph Klemm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
