Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » JavaServer Faces » JSF message bundle auto-complete with localization?
JSF message bundle auto-complete with localization? [message #474853] Fri, 13 July 2007 15:58 Go to next message
Eclipse UserFriend
Hello,
in my project I use localized message bundles. In this case I have
package.name_de.properties
package.name_en.properties
In the jsp I load the bundle with <f:loadBundle basename="package.name"
var="myBundle"/>
Because the real name of the bundle ist with the language at the end (_de,
_en) the jsp validator says "myBundle cannot be resolved". This is also why
I can't use the auto-complete function.
The message bundles are included in the faces-config.xml
Is there a chance to get the auto-complete function to work with
localization?

If I rename to package.name.properties everything works fine. But then I
have no localization.
Eclipse is current 3.3 with europa wtp

tanks, Tobias

[Updated on: Thu, 30 December 2010 18:09] by Moderator

Re: JSF message bundle auto-complete with localization? [message #474856 is a reply to message #474853] Mon, 16 July 2007 19:33 Go to previous message
Eclipse UserFriend
Hi Tobias,

We have a known issue with respect to bundle localization:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=145288

For now, your best workaround is to have *both* the default
(blah.properties) and the localized (blah_de.properties). The
content-assist and validation do not use the localized values anyway (only
the keys), which need to be the same in both files.

A good practice here might be to develop using the default properties file
and then localize when you are getting to deployment.

We are looking into fixing this issue. Please CC and comment on the bug
if this is a high priority issue for you.


--Cam
Re: JSF message bundle auto-complete with localization? [message #613094 is a reply to message #474853] Mon, 16 July 2007 19:33 Go to previous message
Eclipse UserFriend
Hi Tobias,

We have a known issue with respect to bundle localization:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=145288

For now, your best workaround is to have *both* the default
(blah.properties) and the localized (blah_de.properties). The
content-assist and validation do not use the localized values anyway (only
the keys), which need to be the same in both files.

A good practice here might be to develop using the default properties file
and then localize when you are getting to deployment.

We are looking into fixing this issue. Please CC and comment on the bug
if this is a high priority issue for you.


--Cam
Previous Topic:BEA releases WebLogic Server Tools for Eclipse 3.3
Next Topic:WTP 3.0 Release Themes DRAFT document published...
Goto Forum:
  


Current Time: Wed Jul 23 07:31:04 EDT 2025

Powered by FUDForum. Page generated in 0.05283 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly