I see, but why can't you initialise all your plugin libs upon the first request? Does this really hurt a lot performance-wise? Sorry, but I'm just being curious ...
> -----Original Message----- > From: Eckenfellner Klaus [mailto:[EMAIL PROTECTED] > Sent: Friday, July 20, 2007 11:56 AM > To: users@tapestry.apache.org > Subject: Re: component export message properties to global / > application catalog > > sorry my fault .... > > > you should be able to access your components msg-catalog from the > > navigation/border-component via IComponent.getMessages() Does that > > help? > > plugins are realized as !!! component-libraries !!!. problem > is that library-resources (library-global-catalog and > specification) are parsed the first time the library is used. > > but in my navigation solution i need the translation BEFORE > any of my library-information is parsed, exceptionally the > border-library which includes THE navigation logic. > > therefore IComponent.getMessages() doesn't work for me. > > > Also, you components/pages could be required to implement some > > interface Named {getDisplayName(Locale);} > > already done, but also not useful for this case ... reason see above. > > any other suggestions? > > --- > > [EMAIL PROTECTED] wrote: > > 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: users@tapestry.apache.org > >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
