I tend to believe that it is possible the XML parser is thinking it has a
pointer to a schema, and trying to open it? (or some such) Xerces folks,
any comment? Certainly the XSLT processor is not trying to open the URL.
-scott
If you look at javax.xml.transform, you can do what is termed an identity
transformation, which is essentially serialization. This allows you to
serialize SAX events, DOM trees, or re-serialize a stream. As a serializer
it is a bit limited in it's ability to handle doc type stuff, but in other
w
> If it helps, the xerces-j team now posts it's release plans in CVS (see
xml-xerces/java/RELEASE-PLAN-1.x).
Thanks, I didn't know that. That's a big help, and should at least allow
us to better plan our own releases. :-)
-scott
Ah... let me take this opportunity...
It would be great if the Xerces developers could give a heads-up to the
other projects a few days before doing a release, so we can do some extra
integration testing beyond what our smoketest does in Gump, and also so we
can coordinate our releases with yours
You should probably send this message to xalan-dev. The doctype processing
is dynamic by default... if it's there you should be having the dtd
processed and the document validated. If you are using ID attributes with
the id() function you need DTD processing, or if you want default
attributes.
Ross Burton <[EMAIL PROTECTED]> wrote:
> Having spent all day upto my arm pits in bits of cocoon, xerces and
> xalan, I've come to the conclusion that tracking down bugs in bits of
> cocoon can be nearly impossible at the moment. How would you guys feel
> about us starting to use JUnit to run unit
