sure that @Property anotated members can be protected??? i don't believe. can anybody confirm?
Am 07.08.2014 um 16:38 schrieb Muhammad Gelbana: > I would have 2 private properties for each class with different names. Or > have one protected member variable in the parent class. > > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana > > > On Thu, Aug 7, 2014 at 5:05 PM, D.R. <d.re...@googlemail.com> wrote: > >> Hi, >> >> i am facing an issue while upgrading T5.2.6 to 5.3.7 when a Pageclass >> (or component) extends. >> >> In the superclass, a have a @Property called "asdf" and the subclass has >> also that @Property called "asdf". >> >> Both are "private" and it worked without problems in 5.2.6 >> >> With 5.3.7 i get: >> [ERROR] ioc.Registry Unable to create new accessor method public >> com.pipapo.Bsdf getAsdf() on class com.pipapo.Csdf as the method is >> already implemente d. >> >> I checked the release notes, but it does not seem, that "protected" is >> now allowed for @Property anotated variables. >> >> Why did this behaviour has changed? >> >> What is the best practise to deal with that issue? >> >> >> Kind regards >> David >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
