Hi all.

Suppose I have some GUI form which uses a ResourceBundle to load its strings.

ResourceBundle.getBundle() is being used to actually get the strings.
In fact, the code which does this is code generated by Matisse under
NetBeans, and there appears to be no direct way to customise that
detail (though I am not yet a Matisse expert, either.)

Now suppose we need to support translations of the resources.  Any
translations we ship out of the box are easy -- we can put the
Bundle_xx_YY.properties files at the appropriate location and it will
be on the classpath, so it should load correctly.  (Whether this is
the right thing to do under OSGi is another matter entirely of
course...)

But what about support for additional languages in separate bundles?
My own bundle won't (can't?) have a dependency on some bundle which
was built in the future, so it won't see the properties file on the
classpath unless I do something special to get around this.

Presumably this is a common situation in OSGi, so there must be a
proper solution to the problem.  But I haven't yet seen an example of
how to do it so I thought I would check here to see if anyone else had
walked this path before.

TX

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to