My mistake! I have put the element inside the
element.
Anyway, the behavior remained the same -- it still fails erratically and
it still takes a long time to complete :-(
Adrian Herscu wrote:
> It took me a long time to experiment with this.
> Here is the result:
> Property 'org.apache.xerces.
It took me a long time to experiment with this.
Here is the result:
Property 'org.apache.xerces.xni.parser.XMLParserConfiguration' is not
recognized.
Any idea how to enable the caching feature through the ANT interface?
Adrian.
James Abley wrote:
> Try turning on grammar caching.
>
> http://xml.
Prashant wrote:
Steve Loughran wrote:
You have to use different mapping the xmlns to the
relevant doc. You probably always need a local copy because for a long
time, the public webapp xsd didn't allow + in a mime type, like
application/soap+xml.
I am not sure i understand what you mean. Can
Prashant wrote:
Steve Loughran wrote:
Ant 1.7's extension to sets things up
right for all nested elements.
If you cannot use the beta, look at the source, see how we set up the
property
http://apache.org/xml/properties/schema/external-schemaLocation
Thats neat.
I googled and came up wi
Steve Loughran wrote:
Ant 1.7's extension to sets things up
right for all nested elements.
If you cannot use the beta, look at the source, see how we set up the
property
http://apache.org/xml/properties/schema/external-schemaLocation
Thats neat.
I googled and came up with this[1] explan
Steve Loughran wrote:
It turns out that all J2EE 1.4 XSDs belong to same namespace [2].
yeah, that is just silly. Take it up with javaee-spec-feedback at
sun.com. The more people who complain about this, the more likely
someone will come to their senses.
Umm, Ok. I see where this is goi
Adrian Herscu wrote:
Prashant wrote:
And it takes it a very long time to complete (almost ten minutes for
70-80 XML files).
Could't you use to locate the XSD schemas locally instead of
http download, which perhaps is taking time.
Does it work for XML schemas? From the documentation, and
Adrian Herscu wrote:
Prashant wrote:
And it takes it a very long time to complete (almost ten minutes for
70-80 XML files).
Could't you use to locate the XSD schemas locally instead of
http download, which perhaps is taking time.
Does it work for XML schemas? From the
Prashant wrote:
>
>>And it takes it a very long time to complete (almost ten minutes for
>> 70-80 XML files).
>
>
> Could't you use to locate the XSD schemas locally instead of
> http download, which perhaps is taking time.
Does it work for XML schemas? From the documentation, and I think th
>And it takes it a very long time to complete (almost ten minutes for
> 70-80 XML files).
Could't you use to locate the XSD schemas locally instead of
http download, which perhaps is taking time.
-Prashant
Adrian Herscu wrote:
Hi all,
I am using the task in a Maven Ant mojo that validate
Try turning on grammar caching.
http://xml.apache.org/xerces2-j/faq-grammars.html#faq-4
I would imagine by doing something like this:
value="org.apache.xerces.parsers.XMLGrammarCachingConfiguration" />
or:
value="org.apache.xerces.parsers.XMLGrammarCachingConfiguration" />
Cheers,
James
Hi all,
I am using the task in a Maven Ant mojo that validates XML
files against XSD schemas.
http://xml.org/sax/features/validation"; value="true"/>
http://apache.org/xml/features/validation/schema";
value="true"/>
http://xml.org/sax/features/namespaces"; value="true"/>
E
12 matches
Mail list logo
