I know from a "user" perspective I'd like to have things be able to default all the way out to symbol / global properties file definitions when developing libraries and such if possible....
There may be some performance or other internal framework decisions / reasoning behind it but I started to slowly implement these features in T4.1.x as well with good results so far. On 10/19/07, Dan Adams <[EMAIL PROTECTED]> wrote: > So right now I have a situation where I need my library to provided some > default values for some things it provides. The natural place for this > seems to be FactoryDefaults. The problem is that certain things are only > looked up in the component messages when determining defaults and it > doesn't appear that symbols and included when searching for messages > (ComponentMessageSourceImpl uses an AssetFactory and the application > properties file). So the question is: > > Is it appropriate to have the global SymbolSource included when looking > for component messages? Perhaps after the assets and application > properties file? > > Some background on the issue: > I'm adding a validator that takes an optional constraint. Rather than > changing Validator to support this I just want to include a blank > default constraint value for the validator in the library that > contributes it. But I know this issue of looking up defaults is going to > come up for other components. > > -- > Dan Adams > Senior Software Engineer > Interactive Factory > 617.235.5857 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
