I appreciated your patch to automatically expose injections & such as properties, but I strongly believe that any addition to the component's public API should be explicit, thus @GenerateAccessors. The desire to be explicit about API goes further for components where templates may include property expressions that reference properties, and (being outside Java code) you can too easily break things by refactoring. The @GenerateAccessors annotation serves as a reminder to track down references in the template.
On Sun, Mar 2, 2008 at 10:28 AM, Davor Hrg <[EMAIL PROTECTED]> wrote: > just tried it,... works like a charm :) > > Davor Hrg > > > On 3/2/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > Oops. Accidentally reformatted some code. > > > > On Sun, Mar 2, 2008 at 9:21 AM, <[EMAIL PROTECTED]> wrote: > > > Author: hlship > > > Date: Sun Mar 2 09:21:16 2008 > > > New Revision: 632791 > > > > > > URL: http://svn.apache.org/viewvc?rev=632791&view=rev > > > Log: > > > TAPESTRY-2216: Add a @GenerateAccessors annotation for fields to create > a getter and setter method > > > > > > Added: > > > > tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry/annotations/GenerateAccessors.java > > > > tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry/internal/transform/GenerateAccessorsWorker.java > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
