I haven't implemented the InfrastructureOverride service yet; there's
been other fish to fry. If you try and contribute a conflicting
ComponentMessagesSource, you should see an error on the console
explaining that the conflicting definition was discarded. It's not
deterministic (or at least, not predictable) which definition
(Tapestry's or yours) will be used!
On 3/3/07, SergeEby [EMAIL PROTECTED] wrote:
Hi
I tried to override the default ComponentMessagesSource by creating a
contribution in my module (tapestry.ComponentMessagesSource) and a new
builder method, but it doesn't seem to work.
Am I missing something?
/Serge
--
View this message in context:
http://www.nabble.com/T5-Message-Catalog-Override-tf3341408.html#a9293102
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
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]
