"Steve Loughran" <[EMAIL PROTECTED]> wrote on 24/03/2002 06:50:43 PM:
> > I have just been playing with XmlCatalog, and very nice it is too to be able > to reuse references. However, we do now need the <xmlvalidate> task to add > support for the datatype too, so that you can share the same dtd between > validation and styling. Sounds good. > Also > > 1. catalog files? That'd be nice to share stuff over projects. you could > just have a big list of URIa and their local versions Yep, sounds good to me. > 2. resource loading with a <classpath> element? <xmlvalidate> can map a > publicID to a resource, but only in the current classpath, so you have to > have things like j2ee.jar in ant\lib. Good idea. > 3. (a followon issue) what do we need to do get XML Schema to work? > > I think setting compiler="xerces" is enough to get schema based XML files to > validate, but uri resolution is another matter. When I run it the log goes > > [xmlvalidate] Could not resolve ( publicId: , systemId: sample-file.xsd) to > a local entity I haven't looked @ XMLValidate enough to know if it does uri resolving. > -Steve While we're on this topic, do we want a core ant task to pre-req xml-commons' jar file? -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://www.multitask.com.au/developers
