RE: setTextContent

Frell! (*slaps myself for using Farcape reference*) I read the specification again. And I think I got it this time. http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030226/core.html#Node3-textC ontent "When it is defined to be null, setting it has no effect." Content is defined to be null for DO

setTextContent

Hi all. With the long discussion about getTextContent going I was reading the DOM specification and put the code together for setTextContent as well. You can't have one without the other. They are like peas and carrots (*slapping myself for using Forrest Gump reference... again*). Anyway here it i

Re: Cannot open library

Did you add the path where the libarries located to LD_LIBRARY_PATH ( or SHLIB_PATH)? you may run ldd on DOMcount to see if the libxercesc is resolved or not. Rgds, PeiYong - Original Message - From: "Doug Chinnery" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 03, 200

Cannot open library

I've downloaded, built and installed the xerces-c library. As expected, it created 3 shared libraries in my /usr/local/lib directory, called: libxerces-c.so@ libxerces-c.so.22@ libxerces-c.so.22.0 When I try to run my program I get the following error: dynamic linker : ./CreateDOMDocument : er

SAX: need to parse attribute values with namespace prefixes

Hi All, It seems there may be a need to expose some things in Xerces-C++ public API that are currently considered private. We are writing a SAX based SOAP C++ engine (why our own is a separate story), and we need to interpret attribute *values* that contain namespace prefixes: http://www.w3.org/

RE: EntityResolver doesn't receive the baseURI (implementation questions)

Alright, that didn't quite work sadly, as the base class overload is always called. Tacking a slightly different tack, so far I've: - Added EntityResolver2 as described at http://sax.sourceforge.net/apidoc/org/xml/sax/ext/EntityResolver2.html - Added the feature flag http://xml.org/sax/features/

DO NOT REPLY [Bug 18668] - runConfigure should look more extensively for getopt and fail more intelligently

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 18668] - runConfigure should look more extensively for getopt and fail more intelligently

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: Adding RefCount support to DOMNode (was Next release)

If I understand correctly, the new proposal has nothing to do with the underlying DOM implementation. The proposal is to add two new non-standard extensions to DOMNode. My concern is that we are mixing implementation issues with standard spec compliance. The DOMNode and its underlying DOM tree repr

DO NOT REPLY [Bug 18668] New: - runConfigure should look more extensively for getopt and fail more intelligently

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: startCDATA Section Event is not getting fired..

Thanks for the answer Khaled. It worked for me. Raj... -Original Message- From: Khaled Noaman [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 12:05 PM To: [EMAIL PROTECTED] Subject: Re: startCDATA Section Event is not getting fired.. startCDATA and endCDATA are lexical handl

Re: startCDATA Section Event is not getting fired..

startCDATA and endCDATA are lexical handler events and you need to set your handler as the parser's lexical handler. e.g. parser->setLexicalHandler(defaultHandler); Khaled "Avula, Raj" wrote: > Hi, > I have a SAX Parser implementation for processing XML where in > I have a class that

RE: Adding RefCount support to DOMNode (was Next release)

That's exactly what we proposed: the possibility to add reference counting, but not enforcing it (not built in --> empty implementation by default). Which will have no performance impact at all, but adds the possibility to add reference counting at least for other implementations. And since Xerce

RE: Adding RefCount support to DOMNode (was Next release)

I certainly agree that reference counting should not be built in nor should custom memory handling. Atleast the model should be open enough for people to add the cost of reference counting if they please but should not be built in. Similarly we should be able to manage the memory more effectively l

startCDATA Section Event is not getting fired..

Hi, I have a SAX Parser implementation for processing XML where in I have a class that is derived from DefaultHandler. and I am using SAX2XMLReader to parse the XML file. But the problem is if CDATA section is present in the XML, startCDATA and endCDATA events are not getting fired. Is t

DO NOT REPLY [Bug 6959] - Parsing from Memory crashes when multiple threads are running

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_bug

Re: Adding RefCount support to DOMNode (was Next release)

I have not looked at the proposed changes. The question here is what do people want. We had a version of DOM that used reference counting [1] which is currently deprecated. People were complaining about how the the DOM was very slow. The new DOM design was introduced with performance in mind, and I

Re: DOMInputSource (was: EntityResolver doesn't receive the baseURI)

A while back, I posted a note [1] on how the introduction of DOMInputSource and DOMEntityResolver will affect the Xerces-C++ internal components. There was not much of a response. I hope that this note will give people a good overview of the how Xerces-C++ works internally. We currently have two in

RE: Adding RefCount support to DOMNode (was Next release)

For the question at hand: It turns out that it might actually be useful >> to >> have a 2.3 release come out reasonably soon (early-mid May) because some >> fairly important features should be in by then (most importantly, a scheme >> to enable users to have the parser get memory from their own he

DO NOT REPLY [Bug 6959] - Parsing from Memory crashes when multiple threads are running

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_bug

RE: EntityResolver doesn't receive the baseURI (repost)

My reading of it was that you need an overload for setEntityResolver that takes an EntityResolver2 and does the right thing dependent on if you have ER2, ER, or nothing and if the appropriate features flag is set. I was planning on implementing it in this fashion. Does this seem OK? Mark >

Re: Adding RefCount support to DOMNode (was Next release)

I'd like to solicit comment from other committers and stakeholders about this proposed patch. If people agree, I'm happy to commit it. The basic question is: - Is it proper/okay to add several additional "experimental" interfaces to the DOMNode class that will enable use of reference counting

Re: DOMInputSource (was: EntityResolver doesn't receive the baseURI)

> "Gareth" == Gareth Reakes <[EMAIL PROTECTED]> writes: Gareth> Apologies, I did not mean this to sound as if I was Gareth> expecting you to provide anything. I really do mean that I Oh, I didn't interpret it like that. I was actually intending to write the code some time in the futur

Re: Next release

Hi David, Gareth and all, One of the things I'm hoping to do in the next week or so is to share a list of the work items that the folks from IBM are planning to focus on in the next while, including when we thought it might be nice to have a release. This way, I'm hoping other folks (committers a

Re: DOMInputSource (was: EntityResolver doesn't receive the baseURI)

Apologies, I did not mean this to sound as if I was expecting you to provide anything. I really do mean that I can do this in short order if this is helpful to you and is all that is required to be helpful. By new spec I was referring to the one released at the end of Feb. Gareth On 3 Apr 20

RE: RFC: Schema annotation support

Hi Richard, Kiran and Gareth, A few things: 1. I think Kiran's problem is very significant. If we're to expose an interface returning XMLCh *, then it should preserve XML tags, namespace decls etc.; I think this could be provided for relatively easily by using the DOMWriter. 2. The problem I

Re: DOMInputSource (was: EntityResolver doesn't receive the baseURI)

> "Gareth" == Gareth Reakes <[EMAIL PROTECTED]> writes: Gareth> I can change the interface over to the new spec in fairly Gareth> short order if that would be helpful (or you could provide Gareth> a patch). Is this all that would be required? Yes. (new spec? That was the spec way

Re: DOMInputSource (was: EntityResolver doesn't receive the baseURI)

I can change the interface over to the new spec in fairly short order if that would be helpful (or you could provide a patch). Is this all that would be required? Gareth > I've been meaning to mention this for a long time now. The official (? > is 3.0 Load/Save live now) DOMEntityResolver re

DOMInputSource (was: EntityResolver doesn't receive the baseURI)

> "Gareth" == Gareth Reakes <[EMAIL PROTECTED]> writes: Gareth> Hi, sorry about the lack of response the first time. Is Gareth> there a reason why you can't go over to use the official Gareth> DOM stuff? If so perhaps we should have 2 constructors so Gareth> we don't break back

RE: EntityResolver doesn't receive the baseURI (repost)

Right, got it this time, thanks :) > -Original Message- > From: Alberto Massari [mailto:[EMAIL PROTECTED] > Sent: 03 April 2003 15:59 > To: [EMAIL PROTECTED] > Cc: Mark Weaver > Subject: RE: EntityResolver doesn't receive the baseURI (repost) > > > At 15.35 03/04/2003 +0100, you wrote: > >

RE: Next release

Thanks for the reply, I guess I have no excuse for delaying this any longer :) -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 10:19 AM To: '[EMAIL PROTECTED]' Subject: Re: Next release Hi, its definitely more than a few weeks. On t

Re: Next release

Hi, its definitely more than a few weeks. On top of that there will be very little work for you to do to go between 2.2 and 2.3. Gareth On Thu, 3 Apr 2003, David Schulze wrote: > Anyone know a more solid date than "Fall 2003" for the next release of > Xerces? It would be version 2.3.

Next release

Anyone know a more solid date than "Fall 2003" for the next release of Xerces? It would be version 2.3.0 I'm planning on updating our code base from 1.7.0, but if 2.3.0 is coming in a few weeks I'll wait for that instead of going to 2.2.0. Thanks David Schulze DeLorme Mapping Yarmouth, ME, USA -

RE: EntityResolver doesn't receive the baseURI (repost)

At 15.35 03/04/2003 +0100, you wrote: Didn't get any response on this the first time, Strange, I did answer your e-mail In any case, what I was telling you is that the EntityResolver interface is a standard SAX interface, and I guess nobody would like to have it changed. The proper way to add

RE: EntityResolver doesn't receive the baseURI (repost)

Hi, sorry about the lack of response the first time. Is there a reason why you can't go over to use the official DOM stuff? If so perhaps we should have 2 constructors so we don't break backwards compatibility. How does this sound to you? Gareth -- Gareth Reakes, Head of Product Devel

RE: mail archives

I get it! I didn't realize there was another link. I always use the one at http://xml.apache.org/xerces-c/index.html. -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 9:20 AM To: '[EMAIL PROTECTED]' Subject: RE: mail archives Hi Jesse,

RE: EntityResolver doesn't receive the baseURI (repost)

Didn't get any response on this the first time, perhaps to be slightly more clear, when parsing: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en"> A A my entity resolver will receive calls to resolve: http://www.w3.org/TR/xhtml1/DTD

RE: mail archives

Right, I do have permission to change the link from the front page. Does everybody think that it should point to http://marc.theaimsgroup.com/?l=xerces-c-dev rather than a list that does not work? Gareth On Thu, 3 Apr 2003, Gareth Reakes wrote: > Hi Jesse, > > thanks for that. The p

RE: mail archives

Hi Jesse, thanks for that. The problem I was seeing was from the link off the mail archives page on xml.apache.org. I will see if I have access to change the link. Gareth On Thu, 3 Apr 2003, Jesse Pelton wrote: > I don't have any problem reaching them at > http://marc.theaimsgroup.c

RE: does Xerces-C support XPointer?

I don't know of any either. There was some talk on about making Pathan 1 support xpointer. I will try to chase up the person who suggested it and see if they got anywhere. Gareth On Thu, 3 Apr 2003, Erik Rydgren wrote: > Well no. Xerces does not support XPointer. > And me personally doesn't

RE: does Xerces-C support XPointer?

Well no. Xerces does not support XPointer. And me personally doesn't know any other cross platform XML parser that does. Anyone else that does? / Erik -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: den 3 april 2003 15:51 To: [EMAIL PROTECTED] Subject: does Xer

RE: does Xerces-C support XPointer?

The Xerces project tends to focus on implementing the DOM. Xalan adds XSLT and XPath, but so far as I know, not XPointer. There may be XPointer add-ons out there, but I'd have thought they'd turn up in the archives. According to its Web site, libxml2 (http://www.xmlsoft.org) supports "most of" XPo

does Xerces-C support XPointer?

okei, I search the mail archives with the keyword 'xpointer' and found the same question posted in May 2001 with the answer NO. Hope there's a change now... if it is still not supported, which a kinda suspected since it's not listed as a feature: ARCK. Anyone can suggest me a cross-platform XML

RE: mail archives

I don't have any problem reaching them at http://marc.theaimsgroup.com/?l=xerces-c-dev at the moment. I haven't had need to try in the recent past, though, so maybe they've just come back up. -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:

RE: xerces shared lib size

Well you need a static library if you want to link to it statically. The standard binary builds of Xerces is a runtime library. You'll have to download the source and build the staticlibrary yourself. Someone (I do not remember who) on this list did some work a while ago to simplify building Xerces

mail archives

Does anyone know why the archives have been down for so long? Gareth -- Gareth Reakes, Head of Product Development +44-1865-203192 DecisionSoft Limitedhttp://www.decisionsoft.com XML Development and Services --

Re: Any way to check for open child nodes before using release?

Hi, you can not do this although I recall that someone on the list was implementing something which could solve your problem. Anyone want to own up? Gareth On Wed, 2 Apr 2003 [EMAIL PROTECTED] wrote: > > I was wondering if there is any way to check whether any references to > child n