help required

hi, i am totaly new to xml, dom and sax. I want to implement a xml verifier. Given a dtd, and a xml file it will tell whether there is any discripency or not.. I don't want give a DOCTYPE specifcation in the xml document. I want implement it using sax and c++. Plz, help me with regards bhowmick

DO NOT REPLY [Bug 8492] - Incorrect HP link options

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 8852] New: - UnixHTTPURLInputStream.cpp includes unneeded file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: XML output

Howdy, This might sound ridiculous but for one major application I wrote a class to provide my basic XML generation needs, my primary storage is a vector and I just put formatted strings into it. When it comes time to send the XML message I call some support methods from the client class(which

DO NOT REPLY [Bug 8492] - Incorrect HP link options

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Schema validation time >25 secs

All, I've been experiencing schema validation time using the DOMParser and SAXParser class greater than 25 seconds. Is it expected to take that long? The XML instance document size is just ~500 bytes, but the combined size of the schemas is ~400 kbytes. When I turn off validation, parsing occur

DO NOT REPLY [Bug 8837] - Parser enters endless loop when schema processing is enabled

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Hi Jason, Looks like you should avoid the handles, stick to the raw pointer interface, and expose release though your interface. > Sorry, I guess I wasn't clear, what I mean is that there will be a > documented way for people to use the smart pointer interface to DOM > that does automatic memory

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Hi Tinny, OK. We are mostly back to what I originally proposed, keep both interfaces, but have the original DOM interface delegate to the IDOM interface. Just to make sure I am not diverging from what you would agree with please let me know what you think of the following: I added these method

DO NOT REPLY [Bug 8837] New: - Parser enters endless loop when schema processing is enabled

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

"Lenny Hoffman" <[EMAIL PROTECTED]> writes: > > The issue is what I would need to do to keep a smart pointer. > > Sorry, I haven't used SWIG. Does SWIG only work with pointers? It isn't a limitation of SWIG, it is an issue of how Perl wraps C/C++ objects/structs, Perl demands a pointer. > Sp

RE: Issue with adding PI to the DOM Tree in the domprint.cpp exam ple.

I got it... I used the insertBefore method of DOM_Node (of the document) and inserted the PI before the documentNode that I got from DOM_Document::getDocumentElement() Thanks for your help... Kevin -Original Message- From: "McFall, Kevin" <[EMAIL PROTECTED]>@SUNGARD Sent:

RE: Issue with adding PI to the DOM Tree in the domprint.cpp example.

Title: RE: Issue with adding PI to the DOM Tree in the domprint.cpp example. I'm using impl.createDocument() to create my document and I'm specifying the document element here (which appears to automatically add it to the document).  When I then add it to the document with appendChild(), I get

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Joseph, I understand your point. But ... If I am going to rename the old DOM and break all my users, I know I will be beaten up to the ceiling and will drive them all crazy (even though it is named version 2). I mean it ... :-( On the other hand, if we are going to promote the 'IDOM' be the st

Re: Issue with adding PI to the DOM Tree in the domprint.cpp example.

Add the PI as a child of the Document node, not a child of the root element. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Hi Jason, > The issue is what I would need to do to keep a smart pointer. Sorry, I haven't used SWIG. Does SWIG only work with pointers? Specifically can perl_sv_setref_pv be modified to take nodes by value instead of by pointer? For example would the following work?: some_wrapper_method () {

Issue with adding PI to the DOM Tree in the domprint.cpp example.

Title: Issue with adding PI to the DOM Tree in the domprint.cpp example. I've modified the DOMPrint.cpp example to create a tree and then let the rest of the example print it out for me... I have an issue with adding a PI to add a style-sheet reference to my output XML document.  When I add it

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

"Lenny Hoffman" <[EMAIL PROTECTED]> writes: > Am I missing something here? Probably, not ;-) It's usually my lack of C++ knowledge. > > To track the underlying C++ objects, Xerces-Perl keeps a pointer > > to the object, so all my method calls will be pointer invocations. > > I don't understan

DO NOT REPLY [Bug 1448] - Xerces-C crashes when locale is not set. in user env

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 7698] - filenames with embedded spaces in schemaLocation strings not handled properly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Hi Jason, > To track the underlying C++ objects, Xerces-Perl keeps a pointer > to the object, so all my method calls will be pointer invocations. I don't understand what the problem is. You can continue to keep a pointer, or you can keep a smart pointer. I have never done any Perl wrappers, bu

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

> > The second question: does a change of this magnitude warrant treating this > > as a major revision and bumping the version to 2.0? > > I don't have any problem to bump to version 2.0. But since Xerces-J has > redesignd their architecture and introduced the idea of XNI and pluggable > pipeli

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

"Lenny Hoffman" <[EMAIL PROTECTED]> writes: > The smart pointer approach should also be easier to explain in the > programmers guide. For example it can be explained that when wishing to > have automated "in use" indication assign returned nodes to handles: > >{ > DOM_Element element

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

"Joseph Kesselman/CAM/Lotus" <[EMAIL PROTECTED]> writes: > Re DOMNode versus DOM_Node naming conventions: I understand the desire to > not break existing code, and I understand the desire to give the new > interfaces the most "standard" name possible, but I'm just a bit nervous > about this part

64-bit build on AIX

All, The XercesC's 64-bit build on AIX 5.1 (with xlC_r 5.02) is now available at http://xml.apache.org/dist/xerces-c/nightly/2002-05-06/, please help verify this new build Rgds, PeiYong - To unsubscribe, e-mail: [EMAIL PR

Re: ld: fatal: Symbol referencing errors.

The Xerces-C++ 1.7 Solaris binary distribution was built on Solaris 6 using Forte C++ 6.2.   If you are using a different compiler, then re-build from source distribution is required.   See http://xml.apache.org/xerces-c/faq-build.html#faq-4 for details.   Tinny   - Original Message --

DO NOT REPLY [Bug 8826] New: - Runtime Error R6025 Pure virtual function call

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Hi Tinny, We have a choice here in how we implement our handles: keep backwards capability with the original DOM interfaces at the cost of maintaining a full dual interface, or sacrifice backwards compatibility with the original DOM, but gain simplified maintenance, and possibly an easier interfa

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOMinterface

Re DOMNode versus DOM_Node naming conventions: I understand the desire to not break existing code, and I understand the desire to give the new interfaces the most "standard" name possible, but I'm just a bit nervous about this particular solution. I think that's going to be a bit error-prone. We

Re: ld: fatal: Symbol referencing errors.

From what I have gathered... The binary distribution basically requires solaris 7 or 8.. There are some libraries that they come with that solaris 2.6 did not. On my 2.6 I had to build from scratch (make sure you have a gcc >= 3.0 or gcc need to be built with --enable-shared). Later, Mike On Mo

RE: Xerces as static Win32 Library

sincerest apologies. incorrect reply address - and thanks for previous help on static xerces   mattbenic I-Imagine | +27 72 1826161 | [EMAIL PROTECTED] Are you an organ donor yet? 0800 22 66 11 -Original Message-From: Matt Benic [mailto:[EMAIL PROTECTED]]Sent: 06 May 2002 04:5

RE: Xerces as static Win32 Library

oy. ju still ere?   mattbenic I-Imagine | +27 72 1826161 | [EMAIL PROTECTED] Are you an organ donor yet? 0800 22 66 11 -Original Message-From: Fribault, Arnaud [mailto:[EMAIL PROTECTED]]Sent: 03 May 2002 04:30To: '[EMAIL PROTECTED]'Subject: RE: Xerces as static Win32 Libr

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

> > BTW, the handles are no longer backward compatible with the original DOM_ > classes, and thus should follow a different naming convention. Since you > are renaming the IDOM_* classes to DOM*, perhaps the handles could be named > DOM*_h. This is just my initial thought, you may have a better

Re: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

> Lenny raises one of two important questions, in my mind: if the current > IDOM* classes are going to be renamed DOM*, what chould the current DOM* > classes be named? I didn't plan to rename the old DOM, as the old DOM are named as DOM_ (e.g. DOM_Node), while the IDOM is planned to be renam

XML output

Hi ! I just wanted to ask if anybody has found a decent approach to generate XML output ?! I am using a SAX2-parser to parse my XML-data-files and I also want to be able to write the data back to a XML-file. I read the threads about creating XML-output by using a content-handler and creating the

RE: Call for Vote: which one to be the Xerces-C++ public supported W3C DOM interface

Lenny raises one of two important questions, in my mind: if the current IDOM* classes are going to be renamed DOM*, what chould the current DOM* classes be named? His proposal is reasonable; we might also consider something of the form DOMH_*, so you only have to scan the prefix to know which inte

ld: fatal: Symbol referencing errors.

Title: Untitled Document hi:   OS version: Solaris 2.6   xerces version: xerces-c1_7_0-SolForCC   When I use xerces library in my program and try to link it, I can't make it correctly. The message is that: Undefined  first referenced