> > As a developer I'm not looking at components in isolation, but rather, > I'm looking at T5 as a framework. So if the framework provdes defaults > and I don't need to, fantastic! Moreover, I don't need to know that > attribute was ever required, for that's now unimportant information. >
Except when the framework can't provide a default and it blows up in your face. :) Especially with value encoders, the framework /tries/ to provide a default, and often can, but it's not guaranteed. Robert > Steve. > > > On 23 August 2011 10:18, Robert Zeigler <robert.zeig...@roxanemy.com> wrote: >> >> On Aug 22, 2011, at 8/229:06 PM , Bob Harner wrote: >>> >>> "In many cases, a ValueEncoder can be generated automatically from the >> >> And this is the crux: in /many/ cases... /can/ be generated. When it can't >> be, you'll still get the exception that it's not bound and must be. >> Ergo: required. :) >> >> Robert >> --------------------------------------------------------------------- >> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
