| JSF message bundle auto-complete with localization? [message #474853] |
Fri, 13 July 2007 15:58  |
 Tobias F
Messages: 35
Registered: July 2009 |
Member |
|
|
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] Report message to a moderator |
|
|
| Re: JSF message bundle auto-complete with localization? [message #474856 is a reply to message #474853] |
Mon, 16 July 2007 19:33  |
Cameron Bateman
Messages: 480
Registered: July 2009 |
Senior Member |
|
|
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 |
Cameron Bateman
Messages: 480
Registered: July 2009 |
Senior Member |
|
|
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
|
|
|
Powered by
FUDForum. Page generated in 0.06173 seconds
] 
Search
Help
Register
Login
Home
