Dynamic locale switching

Question

Hi,
I need to implement dynamic locale switching in my application i.e. the user
is allowed to change the application display language in runtime.
Is there a mechanism in JavaFX to automatically achieve this goal?
I know that I can use e.g. 2d array where every row may be a different language
and each row item could be a translated text and bind the array items to the UI elements.
I have also tried something like:
java.util.Locale.setDefault(newLocale);
StringLocalizer.associate("myapp.Main";, "myapp");but that does not refresh all texts on screen until I update them manually after switching language:
label.text = ##"Text in a label"Is there a way to refresh all visible texts after switching locale?
Thanks,
Dariusz Gadomski

Answer 1

Does each customer mean each user, or are there many users for each customer?
<p>
2) doableIn general you can use a TopLink DatabaseSession for each user/customer. You can use the same TopLink Project but can use a different login for each session you create.
<p>
If you have many users for each customer, you could potentially use a different TopLink ServerSession for each customer and allow the users to benifit from connection pooling and caching.
<p>
If you are using JPA, there is no easy way to do this currently. You could create the ServerSession yourself and then wrap it yourself with the TopLink EnitityManager implementation. You could use the same TopLink Project from your JPA persistent unit ServerSession and use a different login in your new ServerSession. If each customer has only one user then you could use a connection pool with only 1 connection.
<p>
1) a bad idea<p>
This is probably not a good idea. You avoid being able to share resources such as connection pools across your customers, and cannot share data. But it depends on how many customers you have and how distinct they are. Having each customer run on different databases allows you to have a different machine and application server for each customer, which you may need depending on how each customer scales. If you end up having a different server for each customer, then you could just have a single persistence unit in your application and change the persistence.xml or data-source when you deploy a new customer server.
<p>
<p>---
<p>James Sutherland