in the parser classes, and this method
has been added in Xerces 2.2.
Alberto
> Please add accessors to sax2 parser and xml scanner classes
> ---
>
> Key: XERCESC-466
> URL: http://issues.apache.org/jira/bro
xercesc::DOMImplementation *impl =
xercesc::DOMImplementationRegistry::getDOMImplementation(gLS);
xercesc::DOMBuilder *parser =
((xercesc::DOMImplementationLS*)impl)->createDOMBuilder(xercesc::DOMImplementationLS::MODE_SYNCHRONOUS,
0);
xercesc::DOMInputSource* buffer =
new xercesc::Wrapper4In
bject: Getting a parser from a string
Hello,
I am trying to start a parser from a std::string because this is what i
receive from a xml rpc channel.
The problem is that i already have tried to use DomBuilder,
MemBufInputSource with and without wrappers and i can't make it. Could
someone he
Hello,
I am trying to start a parser from a std::string because this is what i
receive from a xml rpc channel.
The problem is that i already have tried to use DomBuilder,
MemBufInputSource with and without wrappers and i can't make it. Could
someone help me with this problem, like suge
Got it, thanks :)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 2005å1æ5æ 15:36
To: xerces-c-dev@xml.apache.org
Subject: Re: Is valid for Xerces parser?
> Hi,
>
> I have an xml document:
>
> fdfds
>
>
> And I use Xerces
> Hi,
>
> I have an xml document:
>
> fdfds
>
>
> And I use XercesDOMParser to parser this documentation. In my thought,
it should be invalid
> for the root tag is not the exactly same, but I got the right dom tree.
After I write this dom tree back,
> it changed
Hi,
I have an xml
document:
fdfds
And I use
XercesDOMParser to parser this documentation. In my thought, it should be
invalid for the root tag is not the exactly same, but I got the right dom tree.
After I write this dom tree back, it changed to:
fdfds
Is it the right behavior of
At 11.09 09/12/2004 -0500, Lin Guo wrote:
Oh, great! thank you!!
But in the second choice, there is no way to directly get an object of
PSVIElement(PSVIAttribute) ?
I remember that "XML Schema API" specifies interfaces for accessing PSVI
through ItemPSVI, ElementPSVI and AttributePSVI.
Hi Lin,
i
Title: Re: how to retrieve psvi information from a parser
Oh, great! thank you!!
But in the second choice, there is no way to
directly get an object of PSVIElement(PSVIAttribute) ?
I remember that "XML Schema API" specifies interfaces
for accessing PSVI through ItemPSVI, Eleme
in xerces-c, how can I do this to get an XSModel object(ptr)?
In Xerces 2.6 you have two choices:
1) plug in your PSVIHandler object using setPSVIHandler(), and process the
handleElementPSVI/handleAttributesPSVI callbacks
2) call setFeature(XMLUni::fgXercesDOMHasPSVIInfo) on the parser; in the
In xerces-java, it is as
simple as:
--
dbf.setNamespaceAware(true);dbf.setValidating(true);dbf.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);dbf.setAttribute("http://apache.org/xml/prope
Hi,
Xiaofan Zhou wrote:
But when I run the code, it never enters into the methods error(...) or
fatalError(...).
Does SAX2Count validate your xml instance ?
Good luck !
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
Message-
From: Vitaly Prapirny [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 1:02 AM
To: [EMAIL PROTECTED]
Subject: Re: SAX parser validation set up
Hi,
Xiaofan Zhou wrote:
> Hi, all,
> I am a new xerces c++ users, and I am working on a project that uses
> xerces c+
Hi,
Xiaofan Zhou wrote:
What else I need to do set up the parser correctly? And how about if
the meta data is an XML schema?
You have to setting up error handler. Please try to process your xml
instance with SAX2Count sample and if it works than compare your sources
with SAX2Count sources
Hi, all,
I am a new xerces c++ users, and I am working on a
project that uses xerces c++ 1.7 SAX parser. I have a question regarding
setting up a validating SAX parser. I did the following when I set up the
parser:
**
SAX2XMLReader*
pParser
[ http://nagoya.apache.org/jira/browse/XERCESC-372?page=history ]
Alberto Massari updated XERCESC-372:
Priority: Major
> Xerces-C++/1.7 parser can not handle % sign correctly
> -
>
>
[ http://nagoya.apache.org/jira/browse/XERCESC-466?page=history ]
Alberto Massari updated XERCESC-466:
Priority: Major
> Please add accessors to sax2 parser and xml scanner clas
[ http://nagoya.apache.org/jira/browse/XERCESC-477?page=history ]
Alberto Massari updated XERCESC-477:
Priority: Major
> Memory Leak in SAX Parser
> -
>
> Key: XERCESC-477
> URL: http://na
[ http://nagoya.apache.org/jira/browse/XERCESC-1072?page=history ]
Alberto Massari updated XERCESC-1072:
-
Priority: Major
> XML Parser doesnt start on Unixware 7.1
> ---
>
> Key:
[ http://nagoya.apache.org/jira/browse/XERCESC-1187?page=history ]
Alberto Massari updated XERCESC-1187:
-
Priority: Major
> Xerces SAX2 parser can not skip xs:any if xsi:nil is used in
:
-
Key: XERCESC-239
Summary: Memory Leaks in the basic parser operation
Type: Bug
Status: Closed
Resolution: WON'T FIX
Project: Xerces-C++
Components:
SAX/SAX2
Versions:
1.5.1
Assignee:
Reporter: BugZilla Maintainer Account
Cr
:
-
Key: XERCESC-416
Summary: Parser crashes when using schema val with missing schema file
Type: Bug
Status: Closed
Resolution: WON'T FIX
Project: Xerces-C++
Components:
Validating Parser (Schema) (Xerces 1.5 or up only)
Versions:
elements), I need my
parser to simply return a string [or a chunk of characters in the
character() interface] for the structure of element A (e.g, that
is, the whole thing including all the tags) , I don't want
to receive the SAX events for the subelements. Is there an easy way
to do this
Hi
All,
I have a need
to do the following:
Suppose I have
an element A that has a sub structures (e.g it has child elements which could
again have child elements), I need my parser to simply return a string [or a
chunk of characters in the character() interface] for the structure
Hello Sir,
We are working for a company , Opus software
Solutions Pvt Ltd, working in financial domain.
We are using xerces-c parsers for our
applications. We are able to download parsers for AIX & solaris
platforms. But we are unable to download the HP version of the parser. When we
> Note that
> the catch block's after the parser->parse don't catch this. However, if
> you modify the DOMTreeErrorReporter::fatalError routine to throw the
> exception (instead of just handling it) then you will get into the
> catch(...) block after parser-&
Hi,
You need to set an ErrorHandler so that errors can be returned to you. If
you modify the DOMPrint to do a parser->parse("") you will get a
FatalError message (which is caught in DOMTreeErrorReporter). Note that
the catch block's after the parser->parse don't ca
Hi All!
I'm trying to parse not existing file, but 'parse' method
does not emit any exception... Simplified code is:
XercesDOMParser* parser = new XercesDOMParser;
try {
parser->parse ("");
} catch (...) {
printf ("error"); // nev
/XERCESC-1226
Here is an overview of the issue:
-
Key: XERCESC-1226
Summary: Parser reports bogus content when parsing
Type: Bug
Status: Resolved
Priority: Major
Resolution: FIXED
Project: Xerces-C
TECTED]
> Sent: den 11 juni 2004 11:46
> To: [EMAIL PROTECTED]
> Subject: RE: Simple SAX-C++-Parser Documentation - Newbie
>
> Thank you, that is the information i needed! I still have problems
with
> the
> namespaces, are they all defined in XercesDefs.hpp or do i have to
i
se the compiler won't find them.
>
> / Erik
>
> > -Original Message-
> > From: Andre Stock [mailto:[EMAIL PROTECTED]
> > Sent: den 11 juni 2004 10:59
> > To: [EMAIL PROTECTED]
> > Subject: RE: Simple SAX-C++-Parser Documentation - Newbie
> >
[EMAIL PROTECTED]
> Subject: RE: Simple SAX-C++-Parser Documentation - Newbie
>
> Yes, i did! And a few problems are solved now, but how can i tell the
> DefaultHandler what to do if an event occured? I recognized that the
> DefualtHandler.cpp file is missing, do i have to implemen
TED]
> > Subject: Simple SAX-C++-Parser Documentation - Newbie
> >
> > Hi!
> > I`ve various problems implementing a simple SAX Parser. The
> > Parser have to
> > read from an XML stream. So if anyone can help me how to start or even
> > better have a sim
:
-
Key: XERCESC-1226
Summary: Parser reports bogus content when parsing
Type: Bug
Status: Unassigned
Priority: Major
Project: Xerces-C++
Components:
SAX/SAX2
Versions:
Nightly build (please specify the date)
Assignee
omments#action_36019
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1226
Here is an overview of the issue:
-
Key: XERCESC-1226
Summary: Parser reports bogus content when parsing
Ty
:
-
Key: XERCESC-1226
Summary: Parser reports bogus content when parsing
Type: Bug
Status: Unassigned
Priority: Major
Project: Xerces-C++
Components:
SAX/SAX2
Versions
:
-
Key: XERCESC-1226
Summary: Parser reports bogus content when parsing
Type: Bug
Status: Unassigned
Priority: Major
Project: Xerces-C++
Components:
SAX/SAX2
Versions:
Nightly build (please specify the date)
Assignee:
Reporter: David
Have you looked at the SAXPrint sample app?
> -Original Message-
> From: Andre Stock [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 09, 2004 6:05 AM
> To: [EMAIL PROTECTED]
> Subject: Simple SAX-C++-Parser Documentation - Newbie
>
> Hi!
> I`ve various proble
Hi!
I`ve various problems implementing a simple SAX Parser. The Parser have to
read from an XML stream. So if anyone can help me how to start or even
better have a simple parser code fragment for my purposes, i`ll be very
grateful for that. I don`t know which classes to use and how they depends on
a general entity. This is never null when
> invoked by a
> >SAX2 parser.
> >
> >I haven't much of a clue how to do that.
>
> It looks like the specs don't take into consideration XML Schema; what
> should "name" contain in that case?
> If this
> > >Then I'm also left with the getExternalSubset() function, which
again, I
> > >don't know where or how to implement.
> >
> > It should probably be handled like the setExternalSchemaLocation is
> > handled; when isRoot is true and the setting has been set, the
> > resolver is
> > invoked and the
he root element.
> Thanks,
>
> Mark
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
[1] http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/load-save.html#LS-LSResourceResolver
[2] http://marc.theaimsgroup.com/?l=xerces-cvs&m=108146308918611&w=2
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
ach
of the many places that have an ER1 resolver installed (via the SAX parser)
having either a further pointer, or a flag, to an ER2 interface.
(Alternatively, they need to be able to get back to the SAX parser that
created them, and then query for the feature, which is beginning to sound
pretty revo
meter:
name - Identifies the external entity being resolved. Either "[dtd]" for the
external subset, or a name starting with "%" to indicate a parameter entity,
or else the name of a general entity. This is never null when invoked by a
SAX2 parser.
I haven't much of a clue h
Replying to myself:
> There's also a problem with the ER2 vs ER method in that you are
> supposed to
> be able to turn off using ER2 via the SAX2 feature
> http://xml.org/sax/features/use-entity-resolver2.
SAX2 spec:
"If a SAX application requires the customized handling which this interface
def
quot; to indicate a parameter entity,
or else the name of a general entity. This is never null when invoked by a
SAX2 parser.
I haven't much of a clue how to do that.
Now I see that we have the old style resolveEntity method, and a new one
that takes an XMLResourceIdentifier. XMLResourc
ver. By installing an entity resolver, the applications
+* can trap and potentially redirect references to external
+* entities.
+*
+* Any previously set entity resolver is merely dropped, since the
parser
+* does not own them. If both setEntityResolver and
setXMLEntityResolver
ling an entity resolver, the applications
+* can trap and potentially redirect references to external
+* entities.
+*
+* Any previously set entity resolver is merely dropped, since the
parser
+* does not own them. If both setEntityResolver and
setXMLEntityResolver
+* are calle
on".
try
{
// reset document pool
parser->resetDocumentPool();
doc = sstate->par
On Apr 6, 2004, at 6:08 PM, Bovy, Stephen J wrote:
You forgot to set the error handler, at least , its not in the code
snippet you posted.
Ok, well, I did set the error handler, I just didn't include the code
for that. That was supposed to be inferred from my comment that the
error handler repo
You forgot to set the error handler, at least , its not in the code
snippet you posted.
parser->setErrorHandler ( errorHandler );
-Original Message-
From: Nick Bastin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004 2:57 PM
To: [EMAIL PROTECTED]
Subject: Parser not failing
documents so that they
should not validate against their schema, but they still get through
the parser. The error handler reports no errors, as well.
--
Nick
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
gzilla/show_bug.cgi?id=28186
Xerces SAX2 parser can not skip xs:any if xsi:nil is used in xml
Summary: Xerces SAX2 parser can not skip xs:any if xsi:nil is
used in xml
Product: Xerces-C++
Version: 2.4.0
Platform: Sun
OS/Version: S
gzilla/show_bug.cgi?id=9325
Please add accessors to sax2 parser and xml scanner classes
--- Additional Comments From [EMAIL PROTECTED] 2004-04-02 20:32 ---
I won't rehash, I have the same issue as Archie and Nassib (see comments above).
This is a show-stopper, we really need that leve
gzilla/show_bug.cgi?id=27991
Parser fails with escape characters in attribute value
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|VE
gzilla/show_bug.cgi?id=27991
Parser fails with escape characters in attribute value
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=27991
Parser fails with escape characters in attribute value
Summary: Parser fails with escape characters in attribute value
Product: Xerces-C++
Version: 1.7.0
Platform: PC
OS/Version: Windows XP
Statu
Hi,
>
>
>
>
You have not given the full schema but this looks a little suspicious to
me. Is maxLength referring to the length of the strings in
the enumerations? If so then both of your examples are longer than 7.
Check this out
Hi all,
Used Xerces Version: 2.2.0
During the validation of a XML file using SAX parser, when xs:list is used,
validation fails.
Is there any way to get the same requirement of having a list satisfied ?
Error Message given by the SAX Parser is
Message: Datatype error
Hi Daniel,
Hello Xerces Core developers,
> I guess we have exactly the samt problem.
Yes, I think so, too.
> >Anyway, maybe some of the validation code of Xerces could be
> improved to
> >report wrong order of child elements before their parent is closed.
> >This would reduce a lot of responsib
gzilla/show_bug.cgi?id=9325
Please add accessors to sax2 parser and xml scanner classes
--- Additional Comments From [EMAIL PROTECTED] 2004-03-17 16:15 ---
I concur with the idea that either getScanner() or some similar method ought to
be publically accessible. In my experience, access to th
Hi Robert!
I guess we have exactly the samt problem.
>In my case to be sure bad XML does not break the SAX handler code I have to
>implement an empty ContentHandler to be run before the real parsing is donne
>just to get hold of validation errors.
What I do is that I don't set any contenthandler
> Hi Robert,
> Xerces does the validation of an element after the element is
> closed, so
> that it has a list of child nodes to look at.
> You will always get parsing errors as soon as they are
> encountered; only
> validation errors will be reported after the endElement notification.
Oh, I s
invalid XML in time, and as a consequence attempts to create a
pice of information in the wrong place (which causes an segfault on Linux).
I have tested the same DTD/XML with an Python SAX parser, which reports the
DTD error in time.
I think, one who implements XML parsing with an SAX interface
I just saw this has been asked yesterday in "SAX2XMLReader and features?"
So my question aims the same problem.
regards,
Robert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
consequence attempts to create a
pice of information in the wrong place (which causes an segfault on Linux).
I have tested the same DTD/XML with an Python SAX parser, which reports the
DTD error in time.
I think, one who implements XML parsing with an SAX interface should be able
to rely on DTD failure
gzilla/show_bug.cgi?id=3240
Doubts if SAX2 parser is thread-safe
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
At 12.59 15/03/2004 +0100, you wrote:
Hi,
I'm having a problem building a Domparser.
The code below run properly qnd after debugging it
exits normally as well.
It seems the problem comes from the transcode method.
If i remove the transcode it returns the corresponding
encoded value but like that i
Message-
> From: David --- [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 15, 2004 2:11 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Dom parser problem with transcode
>
>
> Thanks,
> What would be then the best way to get the element
> values of of the following XML docum
> > -Original Message-
> > > From: David --- [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, March 15, 2004 7:00 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Dom parser problem with transcode
> > >
> > >
> > >
> > > Hi,
al Message-
> > From: David --- [mailto:[EMAIL PROTECTED]
> > Sent: Monday, March 15, 2004 7:00 AM
> > To: [EMAIL PROTECTED]
> > Subject: Dom parser problem with transcode
> >
> >
> >
> > Hi,
> > I'm having a problem building a Domparser
M
> To: [EMAIL PROTECTED]
> Subject: Dom parser problem with transcode
>
>
>
> Hi,
> I'm having a problem building a Domparser.
> The code below run properly qnd after debugging it
> exits normally as well.
>
> It seems the problem comes from the transcod
Hi,
are you aware that getNodeValue on an element returns NULL?
Gareth
--
Gareth Reakes, Managing Director+44-1865-811184
Parthenon Computinghttp://www.parthcomp.com
On Mon, 15 Mar 2004, [iso-8859-1] David --- wrote:
>
> Hi,
> I'm having a problem buildi
Hi,
I'm having a problem building a Domparser.
The code below run properly qnd after debugging it
exits normally as well.
It seems the problem comes from the transcode method.
If i remove the transcode it returns the corresponding
encoded value but like that it return nothing and it
dies after i
How about a combination of SAXParser::error(..., ErrType_Fatal, ...) and
SAXParser::setExitOnFirstFatalError(true)?
Adam Heinz
Senior Software Developer
Exstream Software
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
Is there any way, from within a DocumentHandler, to indicate to the SAX
parser that I don't want parsing to continue? I know I could throw an
exception, but I'd prefer to avoid that if possible.
Sean
-
To unsubscri
:getElementById or something that seems very weird,
namely it seems to find a different element from the one I started
with, which I already know has the sought-after id.
Here is a fragment of the test program where "doc" is the pointer
gzilla/show_bug.cgi?id=22177
The DOM parser doesn't place the allocate the document using the specified memory
manager
[EMAIL PROTECTED] changed:
What|Removed |Added
Stat
gzilla/show_bug.cgi?id=20058
Parser crash when fed with invalid schema
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|VERIFIED|
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2004-01-22 15:06 ---
The file you need to examine is src\xercesc\util\Transcoders\Win32
\Win32TransService.cpp, and more pre
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2004-01-22 12:02 ---
Great! this fix worked. Now I want to know about the changes done so that I
can port it 1.5.1. I
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2004-01-20 15:58 ---
The fix is available only for the latest CVS; if you need to stick with
version 1.5.1, you will h
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2004-01-20 03:38 ---
How to gets the new dll's? was the fix done in 1.5.1 version or later versions.
I never did a buil
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
[EMAIL PROTECTED] changed:
What|Removed |Added
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2004-01-19 08:06 ---
Created an attachment (id=10004)
this is the file responsbile for parsing a xm
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
[EMAIL PROTECTED] changed:
What|Removed |Added
Stat
Alberto thank you so ver much,
You've made things much more clear.
Ed
-Original Message-
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 1:26 PM
To: [EMAIL PROTECTED]
Subject: RE: XML buffer parser help
At 13.08 14/01/2004 -0500, Purdy, Edgar M
, strlen(myXMLString)
, "dummy"
, false
);
parser->parse(memBufIS);
You need to set some options on the parser, but you were already setting
those up when loading from a file.
A second question --
Is there Xerces functionality that will generate a standardized
: Wednesday, January 14, 2004 11:36 AM
To: [EMAIL PROTECTED]
Subject: Re: XML buffer parser help
If you find DOMPrint or DOMCount better suited to your job, just create
a
MemBufInputSource around your string and give it to the "parse" method
of
XercesDOMParser.
Alberto
At 09.11 14/01/2004 -0
If you find DOMPrint or DOMCount better suited to your job, just create a
MemBufInputSource around your string and give it to the "parse" method of
XercesDOMParser.
Alberto
At 09.11 14/01/2004 -0500, Purdy, Edgar M wrote:
I need to parse a buffer.
I have a working Xerces DOM p
I need to parse a buffer.
I have a working Xerces DOM parser in c++ that parses an XML document.
I have to migrate that parser to work with a buffer only. I have to pull value pairs
out of the XML. The nodename and its value.
I don't want to deal with a .xml file. Timing in this applic
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2003-12-29 12:16 ---
It happens with later versions too (Refer description). We tested with 2.2.0
and 2.4.0 ve
ock.
My approach is not correct. But I think I am close. Is there a suggestion to capture
the rest of these tags?
DOMNodeList* personList= 0;
DOMNodeList* childList =0;
DOMDocument* myDocument = 0;
static XMLCh *pOutputEncoding[5];
try
{
par
gzilla/show_bug.cgi?id=25397
XML Parser returned empty string for a node having japanese character on WIN2003
japanese
--- Additional Comments From [EMAIL PROTECTED] 2003-12-22 12:42 ---
This is an old version. Does this happen with the current v
ny way to fix it so it only makes 1 call to characters()?
No; the characters() call is allowed by the SAX specs to be called multiple
times. This could also occur if you had a text node 100Kb big, as the
parser works on internal buffers of less than 50Kb...
Also what is the escape
On Fri, 19 Dec 2003, Curtis Leach wrote:
> what is the escape sequence for "<" & ">" ?
< and >
-------
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EM
Alberto Massari [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 19, 2003 4:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Unexpected errors in SAX2 parser Xerces C++ v2.3.0
>
>
> At 15.53 19/12/2003 -0600, Curtis Leach wrote:
> >In parsing some XML documents, I'm getting t
to characters()? Also
what is the escape sequence for "<" & ">" ?
Curtis
-Original Message-
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Friday, December 19, 2003 4:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Unexpected errors in SAX2 parser Xerces C++
1 - 100 of 619 matches
Mail list logo
