Brian Faull <[EMAIL PROTECTED]> writes: > Trying to implement the solution you list -- but I need to take > input from a local variable. My previous attempt used a > XercesDOMParser rather than DOMBuilder... and XercesDOMParser::parse > was AbstractDOMParser::parse, which took an InputSource (can be > StdIn*, MemBuf*, LocalFile*, ...). DOMBuilder::parse rather takes a > DOMInputSource, which seems that it may only be a file or URL > natively. > > There is a handy class called Wrapper4InputSource which isa > DOMInputSource which can allow an InputSource to be used as a > DOMInputSource. However... Wrapper4InputSource doesn't appear to be > available in XML::Xerces. I didn't see any tests with a > DOMInputSource used, either... Have I missed something, or...?
Aha! I wondered what that class was for (blush) ... The file Xerces.i controls which Xerces-C API classes that I wrap. Currently, this is done manually - I just update the file an a per-need basis. So if a class' header file is not there, XML-Xerces won't know anything about it. I was just thinking that it would be convenient to know what public header files are available and which ones I'm not currently wrapping. I'll add it and commit it to the SVN repository. You can either grab it from there or I can make a dev snapshot tarball. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
