On 1/12/18 11:41 AM, Romain Manni-Bucau wrote:
Hello
Comments inline
Le 12 janv. 2018 20:07, "mandy chung" <mandy.ch...@oracle.com
<mailto:mandy.ch...@oracle.com>> a écrit :
Hi Romain,
I expect no impact to the translation process. Can you give an
example of one resource bundle and its packaged artifact and where
the localized bundles are packaged?
Sure
/opt/App/lib
|- team1.jar/com.company.team1.service
|- team2.jar/com.company.team2.service
`- classes/com.company.team3.service
Where is the root resource bundle? Can you give a name and which is the
application calling getBundle("abc")?
Which one you want to migrate as modules?
Mandy
Assuming service packages use a resource bundle.
Now translations are in http://i18n.company.com/translations and the
team providing the key/values is team4 with no access to team1, team2
and team3 sources normally.
That is why the only solution I saw was a javaagent or mvn plugin
repackaging the app to add bundle providers on the fly but it is not
satisfying compared to java 8 solution :(. It is also not trivial to
do it at build time since it assumes you know the packages at compile
time which can not be the case with such an atchitecture, allowing to
provide translations after a deployment through the service. Doing it
at runtime requires to create another root classloader since you
recreate jars...not satisfying too.
Any solution? Is adding a -XsupportControlProviderForNamedModules not
doable at all?
