There is a service configuration for adding additional bundles, but there is no enforcement of the order. The configuration is not meant for overriding existing messages (that's done in a component message catalog), but instead is meant for adding new bundles from libraries that add additional validator types.
On 2/5/07, Kent Tong <[EMAIL PROTECTED]> wrote:
Kent Tong <kent <at> cpttm.org.mo> writes: > > Howard Lewis Ship <hlship <at> gmail.com> writes: > > > The developer will know the validator type, because they just > > specified it (either in a validate parameter, or with the <at> Validate > > annotation). They will not know, necesarilly, the message key used by > > the validator implementation. As they are not supposed to know the message keys, so there is no way for them to provide a global message bundle to override the validation messages? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
