It was the before: vs. after: ... contributing before: means that the key/values you contributed were themselves overwritten by the default validation messages from the default contribution. I haven't checked the code, but I belive it all would have worked had you ordered it after:Default.
That being said, yes you can see in 5.2 that ValidationMessagesSource is going away in terms of multiple contributions to the Global messages (which itself is now an @Inject-able object, for use in the services layer). The idea was to unify the application messages w/ validation messages, make it possible for libraries to make use of global messages, and make it possible for an application (or even a library) to override the values for messages provided by the framework. On Wed, Feb 2, 2011 at 7:55 AM, Igor Drobiazko <[email protected]> wrote: > Stephan, > > your previous code was absolutely ok and should have worked. So, there might > be another issue with your app, which you probably should fix. > > On Wed, Feb 2, 2011 at 4:05 PM, Stephan Windmüller < > [email protected]> wrote: > >> On 02.02.2011 12:22, Thiago H. de Paula Figueiredo wrote: >> >> >> No. But I am adding the whole default validation messages to the >> >> componentMessagesSource. Could this cause the problem? >> > Have you tried using "after:*" or "before:*"? It's an ordered >> > contribution, so sorting matters. >> >> Using "after:*" works. But I do not need the ValidationMessagesSource >> now, contributing to ComponentMessagesSource did the trick. >> >> Thanks >> Stephan >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
