Yes, that's correct. It scans the classpath looking for @Configured
classes and builds the tree. So we could ship v3 with the documentation
built from the default set of components. Since the tree is more
structurally oriented than content, that tree would only change as you
start to add things like the ruby adapter and the like. Otherwise, it
tends to be pretty static.
On 1/12/10 6:56 PM, Kedar Mhaswade wrote:
> Justin Lee wrote:
>> In the v3 cycle, both tim quinn and I were playing with ways to
>> generate the schema documentation for v3 that we lost after opting
>> for working without the dtd that v2 had. My version (which borrowed
>> ideas from tim's) is implemented as an admin command as opposed to
>> tim's external tool. I'd like to include this command in the v3
>> tree. The project site is http://kenai.com/projects/schema-doc if
>> you want to take a look. I'm attaching a sample of the output.
>> Right now the command is called "create-documenation" but I'm
>> certainly open to name changes. As of now, the only output is html
>> but I've tried to make adding new output formats relatively easy and
>> certainly a dtd/xsd option is needed.
>>
>> Also attached is the jar. You can drop it in your modules dir and
>> restart to test it. The command is run like this:
>>
>> asadmin create-documentation
>>
>> There are a handful of options to play with though nothing
>> significant just yet. There are some interesting changes to be
>> considered (as suggested by Bill Shannon) such as making the HTML
>> output generated for/by the admin gui or at least outputting the
>> content where the admin gui can display it. (Right now it generates
>> in the config dir next to domain.xml.) Anyway, we can hash all that
>> out some other time. Please take a moment to look it over and see if
>> there's anything that'd make it a bad fit. Thanks.
>>
>
> +1. Good feature!
> From what I understand, the generated schema is a reflection of
> @Configured interfaces (available in the modules) at the time of command
> execution. If that's right, is it reasonable to have a "vanilla"
> schema bundled with GlassFish build? (For one, this will make it
> analogous to v2 where the schema used to be available in
> install/lib/dtds/sun-domain_x_y.dtd).
>
> -Kedar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>