Ah ok, now I'm with you! The ValidationMessages bundle isn't contributed to the "global" messages (ComponentMessagesSource). Seems they can only be found if you use the old service directly. Since Tapestry is using this class internally there's no proper replacement for accessing these properties with a replacement service. I don't know the reason why you need to build the original messages yourself (why don't you let Tapestry build them?). Any customization must be contributed in the way I proposed a mail earlier. However, if you contribute the ValidationMessages to ComponentMessagesSource they're kind of cached twice in the system. I looked up the path, try this:
... String path = "org/apache/tapestry5/internal/ValidationMessages.properties" ... Am 07.01.2011 um 10:40 schrieb Stephan Windmüller: > On 07.01.2011 10:32, Christian Riedel wrote: > >> Of course not, that should be the path to your validation.properties >> that you would've had added with the ValidationMessages instead. Put >> your properties somewhere under [...] > > I did not add any custom properties to ValidationMessages in the first > place. All I want to do is have access to the standard validation > messages of tapestry, in this case the one for "required". > > Regards > Stephan > > --------------------------------------------------------------------- > 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
