ResourceBundles - how to locate on Orion

[Fred Flintstone]

Yabba dabba doo,

In doo doo as my JSPs cannot locate the ResourceBundles. Its all
running on Orion 2.0.2

"myfile.properties" is located in WEB-INF/classes and I've also tried
setting an absolute path to it using the CLASSPATH.

In the JSP the file is accessed via the localisation class

<jsp:useBean id="rb" scope="page"
class="packagename.Internationalisation"/>
String testRB = rb.getString("testRB");

The error thrown is:
java.util.MissingResourceException: Can't find bundle for base name
workbench, locale en_EN

The properties file can't be found. Does anyone have any ideas? All
help appreciated.

Fred "The Rock" Flintstone

 

[Sudsy]

Fred Flintstone wrote:

The error thrown is:
java.util.MissingResourceException: Can't find bundle for base name
workbench, locale en_EN

en_EN?! I've heard of en_US and en_UK but en_EN?...
Maybe someone has something configured incorrectly.

 

[Tor Iver Wilhelmsen]

en_EN?! I've heard of en_US and en_UK but en_EN?...
Maybe someone has something configured incorrectly.

Cultural differences between England, Scotland, Wales and Northern
Ireland differ enough that they deserve their own Locale settings
perhaps?

 

[Sudsy]

Cultural differences between England, Scotland, Wales and Northern
Ireland differ enough that they deserve their own Locale settings
perhaps?

Nah! Welsh would be cy_UK.

 

[Fred Flintstone]

Nah! Welsh would be cy_UK.

There comes a time in life to take a stand, to rewrite that spec -
en_EN. Yes "maybe someone has something configured incorrectly" - but
it doesn't pick up the default bundles (bundlename.properties) or
alternatively named bundles such as en_US either. This is a cultural
difference between web servers (ORION vs OH GOD ANYTHING ELSE PLEASE)
I'm a thinkin. - I could be wrong. Any other ideas solutions to this.

Fred "The Rock" Flintstone

 

[Sudsy]

Fred Flintstone wrote:

There comes a time in life to take a stand, to rewrite that spec -
en_EN. Yes "maybe someone has something configured incorrectly" - but
it doesn't pick up the default bundles (bundlename.properties) or
alternatively named bundles such as en_US either. This is a cultural
difference between web servers (ORION vs OH GOD ANYTHING ELSE PLEASE)
I'm a thinkin. - I could be wrong. Any other ideas solutions to this.

I'm just confused because the exception mentions "workbench", your file
is named "myfile.properties" (at least it's in the right place) but
neither of these names appears in the code snippet you provided. How is
the linkage configured, i.e. how/where does the mapping to "myfile" take
place?

 

[Fred Flintstone]

Fred Flintstone wrote:


I'm just confused because the exception mentions "workbench", your file
is named "myfile.properties" (at least it's in the right place) but
neither of these names appears in the code snippet you provided. How is
the linkage configured, i.e. how/where does the mapping to "myfile" take
place?

The job is figured. For all concerned, and possibly future reference,
I had been writing the *.properties files in textpad - it was
convenient - then saving them as *.properties - or so I thought. In
actual fact they were *.txt files but the file extensions were not
enabled for display in Windows and it wasn't picked up - till imported
into my IDE.
Sudsy to answer your query about the names of my properties files - I
was just giving them a generic name to identify them as
<nameoffile>.properties - thanks for taking an interest in the problem
though.

Fred "The Rock" Flintstone

 

[Sudsy]

Fred Flintstone wrote:

The job is figured. For all concerned, and possibly future reference,
I had been writing the *.properties files in textpad - it was
convenient - then saving them as *.properties - or so I thought. In
actual fact they were *.txt files but the file extensions were not
enabled for display in Windows and it wasn't picked up - till imported
into my IDE.

<snip>

Ouch! And to think that M$ was trying to "help" you by hiding the
file extension...
Who says edlin is a dinosaur?!
ps. Glad to hear that you solved the problem.