Hi Russell,
I'm posting my reply to the list. I think I accidently sent my original
email to both you and the list. In general, it's best to post to the list.
The answer is yes, you should use the Xerces DOM if you're going to use the
mutating member functions of the DOM API.
Dave
|---------+------------------------------------>
| | "Russell C. Hadley" |
| | <[EMAIL PROTECTED]|
| | design.com> |
| | |
| | 02/12/2003 03:43 PM |
|---------+------------------------------------>
>--------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: Re: newbe: books/better docs/better samples.
|
>--------------------------------------------------------------------------------------------------------------------------------|
Thanks for the heads up. So the XalanSourceTree doesn't support any
of the createBlah methods in the document interface? (which is why
it's throwing NOT_SUPPORTED_ERR numbered XalanDOMExceptions at me.)
I'm going to be doing XPath queries and document updates programmatically
so I really should be using the Xerces DOM rather that Xalan's.
Right?
Thanks again. -R
David N Bertoni/Cambridge/IBM writes:
>
>
>
>
> Hi Russell,
>
> Are you looking for a book on XPath in general, or one on using
Xalan-C's
> XPath APIs. If it's the former, there are some good books out there,
and
> also a number of web-based tutorials. If it's the latter, I don't know
of
> any books on Xalan-C.
>
> How you create a document is related to how you're going to interact
with
> that document. While you want to modify it? If so, you can just use
the
> Xerces APIs to parse it. If you're not going to modify it, but just
want
> to parse it from an InputSource, you can use Xalan-C's default source
tree
> and parse it through an instance of XalanSourceTreeParserLiaison. There
> will be many samples which do that.
>
> We could always flesh out the XPathAPI sample if you can give an idea of
> what sort of XPath processing you're trying to do.
>
> Xerces does have some serialization code, but it has some problems with
> documents that were created programmatically. You can also use
Xalan-C's
> FormatterToXML to serialize the DOM instance. Take a look at the
> TransformToXercesDOM sample program. It does an XSLT transformation
with
> an instance of a Xerces DOMDocument as the target, then serializes that
> document using some of Xalan-C's utility classes.
>
> Dave
>
>
>
> |---------+------------------------------------>
> | | "Russell C. Hadley" |
> | | <[EMAIL PROTECTED]|
> | | design.com> |
> | | |
> | | 02/11/2003 03:44 PM |
> |---------+------------------------------------>
>
>----------------------------------------------------------------------------------------------------------------------------------|
> |
|
> | To: [email protected]
|
> | cc: (bcc: David N Bertoni/Cambridge/IBM)
|
> | Subject: newbe: books/better docs/better samples.
|
>
>----------------------------------------------------------------------------------------------------------------------------------|
>
>
>
> Newbe looking for some better xalan-c documentation. Maybe a book that
> gives a little background. Specificly for XPath. The generated docs
> aren't giving me enough of a view to figure out how things fit
> together and the XPath samples that come with the src are a little
> thin. I'm able to parse and query a document but I now need to create
> a new doc with a new input source and need to figure the lightest
> weight way to do that. I'm also looking for a way to serialize to
> output the DOM after I've made changes.
>
> Thanks -R
>
>
