Having said that, I still can't get chainedResourceBundles to work. For the moment, I have just created my own version of the properties file that overrides the existing one when deployed.
With error messages, most of the validation listeners attached to widgets in the java code can take an optional message argument that outputs a message from the properties file. If this optional argument is not used, then you get a standard message like 'This parameter cannot be empty' etc.
Hence, if the java code currently uses the optional argument then you can fix the error messages by changing values in the properties file, else the code should ideally be updated to use the optional argument and a patch submitted.
Ideally, all text that appears in the UI should come from the properties file so that it can be globalised & customised, but this can be a bit hit & miss in places.
Chris.....
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have had a request to modify the content center interface
We would like to:
1) Add configurable links to help pages on our intranet
2) Be able to identify who the locking user is (we often get error where publishers are trying to work on pages not locked to themselves)
3) Improve the error messages displayed
4) Change some of the terminology - so instead of saying locked to , say assigned to
Has anyone else been looking at doing anything like this? Does it sound feasible?
Thanks
Luke
Hi Luke,
3 & 4 should be possible by overriding the globalised message properties file - see https://sourceforge.net/forum/message.php?msg_id=3722519
Having said that, I still can't get chainedResourceBundles to work. For the moment, I have just created my own version of the properties file that overrides the existing one when deployed.
With error messages, most of the validation listeners attached to widgets in the java code can take an optional message argument that outputs a message from the properties file. If this optional argument is not used, then you get a standard message like 'This parameter cannot be empty' etc.
Hence, if the java code currently uses the optional argument then you can fix the error messages by changing values in the properties file, else the code should ideally be updated to use the optional argument and a patch submitted.
Ideally, all text that appears in the UI should come from the properties file so that it can be globalised & customised, but this can be a bit hit & miss in places.
Chris.....