Thanks Thiago. Yes it will work like you propose even with the @Property annotation in the subclass (avoiding getEntityB()). The fact that we use the same property name is mainly a convenience for developers according to some internal guidelines.
By the way, is it ok that the 'getOrCreateMethod()' does not check the return type for a given method signature or that deserves a JIRA ? The initial pb was that the code works with 5.1, not with 5.2 because of the new class transformation implementation. Nourredine. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Pb-in-getOrCreateMethod-tp3403357p3403686.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
