Sure. :-)
And forgot to mention in my previous email that we can configure the xml
validation the same way as in v2 through the "deploy-xml-validation"
attribute of "das-config" element. I think this attribute is exposed
through admin console.
There are three possible values for "deploy-xml-validation" attribute:
1. "full": This is the default. The xml validation will be turned on and
the deployment will fail on validation error.
2. "parsing": The xml validation will be turned on and the deployment
will continue on validation error (the error will be logged in the
server.log).
3 "none": The xml validation will be turned off.
- Hong
Anissa Lam wrote:
>
> Hi Hong,
> Thanks for taking care of the admingui app.
>
> Anissa.
>
> Hong Zhang wrote:
>
>> I have just checked in changes to turn on XML validation for standard
>> deployment descriptors in v3. This was turned on by default in v2.
>> You may notice some deployment failures due to xml validation errors
>> afterwards. If so, you should fix your deployment descriptors to
>> conform to the dtds/schemas. I have fixed the admingui app and one
>> case in the Quicklook tests.
>>
>> - Hong
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net For
> additional commands, e-mail: dev-help_at_glassfish.dev.java.net