; -Original Message-
> From: Eckenfellner Klaus [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 24, 2007 8:26 AM
> To: Tapestry users
> Subject: Re: component export message properties to global /
> application catalog
>
> the libId (which equals namespaceId) is set in
in your nav-component,
> couldn't you?
>
>> -Original Message-
>> From: Eckenfellner Klaus [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 23, 2007 10:58 AM
>> To: users@tapestry.apache.org
>> Subject: Re: component export message properties to global
gt; 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.
>>> -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 catal
>
>> -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
>>
>>
;> 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
>>
>&
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
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) a
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 K
