Re: [jboss-as7-dev] i18n
Good general reminder.
FYI, for the description stuff you saw, the pieces are assembled by
invoking on a bunch of implementations of this:
public interface DescriptionProvider {
/**
* Gets the descriptive information (human-friendly description,
list of attributes,
* list of children) describing a single model node or operation.
* <p>
* The implementation must assume that the caller intends to modify the
* returned {@code ModelNode} so it should not hand out a reference
to any internal data structures.
*
* @param locale the locale to use to generate any localized text
used in the description.
* May be {@code null}, in which case {@link
Locale#getDefault()} should be used
*
* @return {@link ModelNode} describing the model node's structure
*/
ModelNode getModelDescription(Locale locale);
}
All the free form text is coming from resource bundles. As we fill out
the missing parts, folks must continue to do it that way.
The "read-resource-description" operation that was used to generate the
output takes an optional "locale" param; if provided we'll use the value
to create the Locale used above.
On 1/25/11 3:47 AM, Heiko Braun wrote:
I was just looking at the example how to retrieve the resources descriptions for the
current domain model tree.
(See Brain earlier post). Many of the resources contain complete and meaningful
description attributes. (Well done.)
I cannot see, wether or not these attributes are served from a localized bundle, but I
want to remind everybody
to build for i18n upfront. We expect the management UI to support different locales early
in the game, to ensure things work properly on the UI side of things. If you could the
prepare the modules you are working on accordingly, it would be a great help.
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat