It seems that some confusion stems from the documentation on the Jakarta
Tapestry site. The Home page talks about the "global message catalog" as
a new feature in 4.x, but the Localization page talks about "Namespace
message catalogs" and makes no mention of it being a new feature to 4.x.
It seems like two different names for the same functionality.
This section adds to the confusion...from the Localization page (link
below)
"For each localization of the base property name, a search of the
following locations takes place.
The page or component specification.
The namespace (library or application) specification for the
namespace containing the page or component.
The global property source. "
How do Namespace & Global differ? They both appear to be defined as
application-level....
"Applications can now have a global message catalog" (from Home
page)
"Namespace message catalogs: It is very likely that you'll have a
number of strings that are used, and re-used, throughout your
application." (from Localization page)
So what's the correct way to define these terms, and should only one term
be used?
Thanks,
- Mike
Here are the links and full text....
Home Page
http://jakarta.apache.org/tapestry/index.html#Tapestry+4.0
Applications can now have a global message catalog, in addition to
per-page and per-component message catalogs. Messages not found in the
component message catalog are searched for in the application catalog.
Localization Page
http://jakarta.apache.org/tapestry/UsersGuide/localization.html
Namespace message catalogs
It is very likely that you'll have a number of strings that are
used, and re-used, throughout your application. Rather than duplicate the
same message keys and localized values in all your page and component
message catalogs, you can put these into your namespace catalog.
Each page and component is part of a namespace, identified by a
library specification or component specification.
The specification may also have a message catalog; for instance,
for WEB-INF/myapp.application, the files would be named
WEB-INF/myapp.properties, etc. Again, the name of the file is based on the
servlet name ("myapp").
Very simple applications may not have an application
specification, but may still have properties, just as if the application
specification existed.
[EMAIL PROTECTED]
12/14/2005 10:32 AM
Please respond to
"Tapestry users" <[email protected]>
To
"Tapestry users" <[email protected]>
cc
Subject
Re: I18N 3.x vs. 4.x
I'd be interested in seeing where it's documented that it works in 3.0.x.
In fact, people have tweaked 3.0.x to make a global message catalog work
(I don't recall the particulars offhand), but out of the box, there is no
such mechanism for 3.0.x. Thus, it /is/ a change (improvement) in
functionality.
If you saw documentation claiming that a global message catalog works out
of the box for 3.0.x, it's wrong.
Robert
> But this global message catalog (aka the namespace catalog) is
documented
> to be working in 3.x. I'm using 3.0.3 and it doesn't seem to work.
> Another user on this list has reported the same problem.
>
> So this shouldn't be considered a change infunctionality, right? or is
the
> documentation wrong & it's only a 4.x feature?
>
> Thanks,
> - Mike
>
>
>
>
>
> Howard Lewis Ship <[EMAIL PROTECTED]>
> 12/14/2005 09:41 AM
> Please respond to
> "Tapestry users" <[email protected]>
>
>
> To
> Tapestry users <[email protected]>
> cc
>
> Subject
> Re: I18N 3.x vs. 4.x
>
>
>
>
>
>
> The only change is that there is now a global message catalog for the
> entire application, which is used when a particular message key is not
> found in the message catalog for an individual page or component.
>
> On 12/14/05, Mark Stang <[EMAIL PROTECTED]> wrote:
>> Hi,
>> Has the mechanism for internationalization changed from 3.x to 4.x?
>>
>> We may have to and I need to know if I should convert to 4.x before or
> after I internationalize.
>>
>> And how much trouble has it been to internationalize applications?
>>
>> thanks,
>>
>> Mark
>>
>>
>
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta 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]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
