Mailing-List: contact myfaces-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <myfaces-user@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: domain of Neal.Haggard@sas.com
 designates 149.173.6.17 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Request for suggestions on Resource Bundle keys?
Date: Thu, 24 Mar 2005 18:09:58 -0500
Message-ID: <45C713F0D0E1114F81A1944E26AB5B3602528A73@MERC21.na.sas.com>
Thread-Topic: Request for suggestions on Resource Bundle keys?
thread-index: AcUwxplKVaOAeCsbRV2rtvEXm6HzSw==
From: "Neal Haggard" <Neal.Haggard@sas.com>
To: "MyFaces Discussion" <myfaces-user@incubator.apache.org>

I noticed in JSF In Action (Mann) that he had all his resource bundle =
keys that he was going to use in his JSF views defined more like =
standard variables than standard resource bundle keys.  For example:

PathNotFound=3DPath {0} not found.

Internally, we have tools which will do internationalization for us, but =
they rely on suffixes on resource bundle keys (namely .txt if it's =
something that should be translated automatically).  So I would have to =
have:

PathNotFound.txt=3DPath {0} not found.

Obviously, I can't use this in a value binding expression (i.e. =
#{myBundle.PathNotFound.txt}) as it will be looking for a .txt attribute =
off the PathNotFound object. =20

I was hoping that maybe I could get away with treating the bundle as a =
map, like:  #{myBundle['PathNotFound.txt']}, however no dice, I'm =
getting a 'Missing' error for keys that are defined that way.

As a note, I wrote in a test key using the syntax that is prescribed, =
and it will appear properly, so it's not that my resource bundle isn't =
being loaded.

Any ideas on how to get around this?

Thanks,

Neal