Jason Untulis wrote:
> Thanks for the ideas. Your suggestion helped to determine my problem was
> that I was trying to use an <xmlcatalog> defined in the top level, rather
> than one embedded in the <xmlvalidate> task. It seems that, while
> <xmlcatalog>s are allowed on the top level and can be used by tasks,
> classpaths cannot be set for them, i.e. they only use the system classpath.
> This seems like a bug to me. I'll try filing this in the next couple days.
Would it be better/easier to have <xmlvalidate>'s classpath used by
whatever <xmlcatalog>'s are nested (if even by refid)?
What other solution did you have in mind for this?
> Side note: the tests in CVS seem pretty simplistic. They don't cover the top
> level case, a jar, a classpath element (as opposed to a classpath attribute,
> which isn't mentioned in the documentation as being supported) or a system
> identifier being used.
Well, we're all human and we write the tests the best we can, but even
in a test-first mode its not expected to write a test for necessarily
every conceivable use on the first try.... :) Patches gladly accepted!
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
