You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Jean-francois Arcand <je...@sun.com> on 2002/08/15 20:02:03 UTC
[5.0] [PROPOSAL] Validation/NamespaceAware
Hi,
based on the mailling list feedback, I would like to propose the
following solution for the XML Parser DTD/Schema validation/namespace
aware problems:
- Add the following attributes in server.xml under the HOST element:
xmlValidation="false"
xmlNamespaceAware="false"
and set them equal to false by default. This way, peoples will be able
to turn it on only if they need it, using the AdminTool or directly in
the server.xml file.
It will still let the door open for:
- "have a separate validation program that can be run on a webapp _before_ it is deployed on tomcat" (Costin)
- keeping validation available when required (Steve)
- etc.
Thanks,
-- Jeanfrancois
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [5.0] [PROPOSAL] Validation/NamespaceAware
Posted by Patrick Luby <pa...@sun.com>.
Jean-François,
I would vote +1 as long as these two HOST attributes are optional
attributes. In other words, if they are missing from server.xml, both
default to "false". I think that is what you are proposing but I just
wanted to make sure.
Patrick
Jean-francois Arcand wrote:
>
> Hi,
>
> based on the mailling list feedback, I would like to propose the
> following solution for the XML Parser DTD/Schema validation/namespace
> aware problems:
>
> - Add the following attributes in server.xml under the HOST element:
>
> xmlValidation="false"
> xmlNamespaceAware="false"
>
> and set them equal to false by default. This way, peoples will be able
> to turn it on only if they need it, using the AdminTool or directly in
> the server.xml file.
>
> It will still let the door open for:
>
> - "have a separate validation program that can be run on a webapp _before_ it is deployed on tomcat" (Costin)
> - keeping validation available when required (Steve)
> - etc.
>
> Thanks,
>
> -- Jeanfrancois
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
_____________________________________________________________________
Patrick Luby Email: patrick.luby@sun.com
Sun Microsystems Phone: 408-276-7471
901 San Antonio Road, USCA14-303
Palo Alto, CA 94303-4900
_____________________________________________________________________
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [5.0] [PROPOSAL] Validation/NamespaceAware
Posted by Remy Maucherat <re...@apache.org>.
Jean-francois Arcand wrote:
> Hi,
>
> based on the mailling list feedback, I would like to propose the
> following solution for the XML Parser DTD/Schema validation/namespace
> aware problems:
>
> - Add the following attributes in server.xml under the HOST element:
>
> xmlValidation="false"
> xmlNamespaceAware="false"
>
> and set them equal to false by default. This way, peoples will be able
> to turn it on only if they need it, using the AdminTool or directly in
> the server.xml file.
Awesome :)
We should also add those attributes to the default server.xml (in
addition to adding checkboxes on the Host page in the admin) so that
people know that they exist.
> It will still let the door open for:
>
> - "have a separate validation program that can be run on a webapp
> _before_ it is deployed on tomcat" (Costin)
> - keeping validation available when required (Steve)
> - etc.
- Doing a TC 3.3 style trick along with background deployment
I think that one looks cool :)
Thanks a lot,
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [5.0] [PROPOSAL] Validation/NamespaceAware
Posted by co...@covalent.net.
Big +1 !
We can have a small ant-based script that can validate a webapp -
find all the XMLs and TLDs and run schema and DTD validation on it.
Another nice thing we could do - if someone has the time - is
adding 'Serializable' to Context and all other config objects and
saving a snapshot. Then reuse the dependency checking from jasper
and check if any of the files changed ( web.xml, jars, tlds ).
On the first load or on change we could validate - and for the
rest just load the .ser object.
But it is not easy - turning validation off by default until
we have a way to avoid duplicated validation is a good solution.
Costin
On Thu, 15 Aug 2002, Jean-francois Arcand wrote:
> Hi,
>
> based on the mailling list feedback, I would like to propose the
> following solution for the XML Parser DTD/Schema validation/namespace
> aware problems:
>
> - Add the following attributes in server.xml under the HOST element:
>
> xmlValidation="false"
> xmlNamespaceAware="false"
>
> and set them equal to false by default. This way, peoples will be able
> to turn it on only if they need it, using the AdminTool or directly in
> the server.xml file.
>
> It will still let the door open for:
>
> - "have a separate validation program that can be run on a webapp _before_ it is deployed on tomcat" (Costin)
> - keeping validation available when required (Steve)
> - etc.
>
> Thanks,
>
> -- Jeanfrancois
>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>