By the way,
Tobago uses also a Resource Management since years, and also uses the
"good old Java style" (with suffix).
We have good experience with that way, with properties, images, scripts,
styles, etc.
Regards
Udo
Matthias Wessendorf schrieb:
Got a response from Ed Burns:
<ed>
This is a well documented and understood shortcoming of the Resource
Handling system. We will address it in 2.1.
</ed>
On Tue, Oct 20, 2009 at 2:05 PM, Grant Smith <[email protected]> wrote:
I prefer the spec's way. I would hate to have to have the resource
identifier as part of each file in the library.. Imaging naming hundreds of
.gif files. This way it's just part of the directory name.
The properties file is just one file per locale, so that's not such a big
deal.
On Tue, Oct 20, 2009 at 1:56 PM, Matthias Wessendorf <[email protected]>
wrote:
Hi,
I am reading SPEC 2.6.1.3 and I am not sure on the localePrefix...
Imagine I am using a "library" in the $WEB_ROOT/resources
so the USA, the resourceIdentifier would be like:
en_US/mycorp/cool.gif
and for Germany, it would be:
de_DE/mycorp/cool.gif
I wonder why it was done this way ?
For the properties files, they syntax is following this schema:
Messages_en_US.properties
Messages_de_DE.properties
Perhaps I am not really understanding the benefit of the JSF 2.0
resource handling, but
why shouldn't a "library" contain multiple images (etc), like:
/mycorp/cool_de_DE.gif
/mycorp/cool_en_US.gif
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Grant Smith
