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: -- Brian Stansberry Principal Software Engineer JBoss by Red Hat