you should be able to access your components msg-catalog from
the navigation/border-component via IComponent.getMessages()
Does that help?
Also, you components/pages could be required to implement some
interface Named {getDisplayName(Locale);}
> -----Original Message-----
> From: Eckenfellner Klaus [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 20, 2007 10:30 AM
> To: [email protected]
> Subject: component export message properties to global /
> application catalog
>
> hi everybody!
>
> short description of my application:
> my application uses tapestry components to create some
> dynamic plugin behavior. tapestry components can be plugged
> in and are registered with the help of a configuration-point
> (hint from marcus schulte thx).
>
> every plugin / component contribute to configuration-point a
> pageName and displayName of page. another component (most
> called border) injects information of configuration point and
> renders some kind of navigation bar.
>
> and here is my problem....
>
> the attribute displayName tells me how the page is called.
> this value is
> key for i18n - message. problem is, that only the
> components, which contribute to configuration-point, knows
> the translation. for example:
> only the login component know how login is called in EN / DE / FR ....
>
> but the message information of the specific component (for example
> login) is not available for the border component (which
> renders navigation).
>
> I need some mechanism to export messages to Application Catalog.
> does anybody have any idea?
>
> thx
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
