Hi Brian,
When you want to validate a schema by itself, it's always useful to
remember that, even if Xerces were able to handle the schema-for-schemas
with no difficulties, you still wouldn't get complete validation of your
schema by directly referencing it. There are all kinds of schema-validity
Hi There-
Stock market got you down? How would you like to own one of the best Internet businesses? Imagine... FREE personalized & Automated e-commerce Web Sites and... a FREE INSTALLATION of a Satellite TV System.
That's Right! Get paid to give them away! It's now possible to save time and make
Joseph Kesselman wrote:
One very strong vote in favor. This would also presumably make it easier
to plug in other "translating" output stages, such as my XNI to DTM
builder or to set up Elena's revalidating pipeline.
True.
XNI's about data flow from component to component. It should be possib
>So perhaps it would be useful to create filters that
>only do the conversion from XNI to DOM trees or SAX
>events. Then the parser classes would use these classes.
>This would make it easier for people to build DOM trees,
>for example, from XNI streams without carrying along
>any of the extra bag
SB wrote:
Will it be possible to make the org.apache.xerces.parsers.DOMParser
of Xerces1.4.4 to implement an XMLFilter, rather than being just a
*handler? This would help other filters get access to the partially
constructed DOM.
I don't think that's a good idea. The DOMParser (and the
SAXParser,
