Re: Less annotation is a GOOD THING

Thanks! Looks like nice way to satisfy my desires :) --- Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > My approach has always been to start from a position > of strength, > which generally means lots of details, such as > exactly what to inject. > It much easier to loosen things up gradually (b

Re: Less annotation is a GOOD THING

My approach has always been to start from a position of strength, which generally means lots of details, such as exactly what to inject. It much easier to loosen things up gradually (by introducing smart defaults) if you start from a state where things are very explicitly defined. In fact, you co

Re: Less annotation is a GOOD THING

I buy into the consistency argument but still do not want to see annotations in the trivial cases. I am talking about consistency of different kind: tool does everything for me till it needs guidance. It is about Sensible defaults philosophy and following conventions philosophy. For example the

Re: Less annotation is a GOOD THING

I'm totally with Pat and Scott on this. For a tool to behave consistently is a critical point, and to do this you should avoid different behaviour without any apparent reason. In the long run the simple routine of performing those little but familiar steps will become automatical for you (believ

RE: Less annotation is a GOOD THING

, 2005 9:05 PM > To: Tapestry users > Subject: Re: Less annotation is a GOOD THING > > I think that those 'little' efforts could and should > be required precisely in the cases you have mentioned. > Most of the time there is no ambiguity and therefore > efforts s

Re: Less annotation is a GOOD THING

I think that those 'little' efforts could and should be required precisely in the cases you have mentioned. Most of the time there is no ambiguity and therefore efforts should not be wasted. In addition to the convenience of the auto wiring such approach will help to avoid typos like @InjectObjec

Re: Less annotation is a GOOD THING

I'm not sure giving the Tapestry engine the power to guess what objects needs injecting is a good idea. What if you specified one of the properties you specified below, but wanted to set it manually from pageBeginRender? Or inject a ServletContext or WebRequest from a different service location?