What does the Scala property look like? Is it just a different naming convention for the getter & setter?
In any case, it probably can be accomplished by extending PropertyAccess. If PropertyAccess returns the correct things, then PropertyConduitSource will build the right code for property expression access. On Fri, Mar 19, 2010 at 8:38 AM, Hugo Palma <[email protected]> wrote: > I've recently started developing a Tapestry application using only Scala and > so far it's been working great. > > One thing that annoys me a little is the fact that i have to annotate all my > classes with the @scala.reflect.BeanInfo so that proper bean getter and > setters are generated and discovered by Tapestry. > What i'd like is to do this in Scala: > > class MyComponent { > var myProperty > } > > and Tapestry would be able to use "myProperty" as a real property, because > it actually is. It's just that Scala doesn't use the java beans convention > for getters and setters name. > > Anyway, i was wondering if you guys agree with adding support for Scala > properties into Tapestry or if that's a direction you don't want to take. > If you agree with incorporating such change, i'll gladly submit a patch with > the required change to make this work. > > Cheers. > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
