The alternative is to have a messages.properties (global or per-package), but we need an established naming scheme, so in the best case it would be like:
ConstantThroughputTimer.displayName=Constant Throughput Timer
ConstantThroughputTimer.delay.displayName=Delay before each affected sampler
ConstantThroughputTimer.throughput.displayName=Target throughput (in samples per minute)
ConstantThroughputTimer.throughput.shortDescription=Maximum number of samples you want to obtain per minute, per thread, from all affected samplers.
I'm not for one or the other option. What's more usual in Java applications?
Q: Is there any tools out there to maintain localization .properties files? There must be one!
-- Salut,
Jordi.
En/na BAZLEY, Sebastian ha escrit:
Is the idea to move all the Bean-related properties from
messages.properties to
<classname>Resources<lang>.properties?
It seems to me that this will result in a lot of property files to create, translate, test and maintain.
I can see that it is useful to be able to have more than one set of property files, but one set per class is rather a lot - would it be possible to combine these in sets at the package (or some parent package) level?
Just a thought ...
S
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
