No, I'm saying you should analyze what values and/or services are needed in each of your scenarios and Tapestry gives you the flexibility to do exactly what you want or need.
On Tue, Nov 20, 2012 at 3:19 PM, bhorvat <horvat.z.bo...@gmail.com> wrote: > hm...so what you are saying is that I should not set a property that will > be > used by other module, but instead copy the method into my 3 modules and > make > it custom for them, right? > > i guess the only problem that I have is code duplication > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Adding-new-properties-from-AppModule-tp5718137p5718139.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 > > -- 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
