> from XMLString.cpp:74:
>
/user/sbhatnag/xerces/xerces-c-src_2_3_0/include/xercesc/util/RefArrayVectorOf.c:
> In destructor
`xercesc_2_3::RefArrayVectorOf::~RefArrayVectorOf()':
>
/user/sbhatnag/xerces/xerces-c-src_2_3_0/include/xercesc/util/RefArrayVectorOf.c:25:
> error:
> Hi all,
> Not sure if this a bug or if I am doing something wrong. I am wrapping
Xerces DOM object
> with XercesDocumentWrapper and using this for xpath expressions.
> This works fine when I am not using namespaces, however it fails with
namespaces.
> I tried to debug this and found that call t
Hi Jason,
Gareth's bug is here:
http://issues.apache.org/jira/browse/INFRA-266
The infrastruture JIRA database is here:
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10410
Dave
[EMAIL PROTECTED] (Jason E. Stewart)
Sent by: "Jason E. Stewart" <[EMAIL PROTECTED]>
04/06/2005 10:
> I downloaded the code last night so it is the latest version of xerces.
> When I run "uname" on my sun box I get the following output:
>
> SunOS pandora 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-60
>
> I have now successfully now compiled xerces with gmake 3.8, gcc 3.3, and
g++
> 3.3
>
> T
> Hi,
>
> I need some help, as I'm not familar with UNIX c++ build.
>
> I downloaded the binary xerces-c1_6_0-AIX43_5.02 from Apache download
site.
> On AIX5, I try to build a sample with the library in this package. But I
get following error:
That version of Xerces-C was built with xlC, so
> Here you are:
>
> virtual void SAXParser::startElement(const XMLElementDecl &elemDecl,
const
> unsigned int uriId,
>
> const XMLCh *const elemPrefix,const RefVectorOf< XMLAttr >
> &attrList,
>
> const unsigned int attrCount,const bool isEmpty,const bool
> isRoot
> I'm trying to figure out how to build a debug version
> of the xerces shared object on linux (bash). This is
> what I do to build the library in general:
>
> //Begin Build
> export
> XERCESCROOT=/home/mydir/xercesc/xerces-c-src_2_5_0
>
> ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket
> -t
> Well,
>
> I've been digging around a lot to understand what Xerces does and does
> not allow and there seems to be some problem with Xerces here. If I
> follow your tip and use the ContentSpecNode I end up in a dead end. I
> can get the ContentSpec, but it doesn't do me much good, all that it
>
> Thanks much for your reply, I still have a few more questions:
>
> Do you mean that I got the source code for xerces-c and ICU and then
> build the projects myself?
> Do I need to modify any source code?
> Once I have the xerces-c and ICU ready, I can just include them in my
> projects and I s
> Make sure you transcode to UTF-8.
>
> Sounds like a good idea, but I'm not sure how. Do I
> have to use ICU? Or is there some way through
> XMLString (or some other xerces class/api) which isn't
> obvious to me?
Look at the class XMLTransService in src/xercesc/util/TransService.hpp
>
> > If
> I'm wondering if I can count on the fact that the
> chars argument to the characters( ) method will be a
> null terminated array?
No, you cannot.
> The documentation seems not to indicate either way,
> but the fact that the length is passed explicitly
> suggests that it is not neccasarily null
> I have taken a look at CreateDOMDocument and made some progress with
> building an 'uninitialized' DOM. However, I can't see how to load data
> in the DOM? i.e. the values that would end up in between the XML tags?
Those "values" are text node children.
> I've had a trawl through the Xerces Cla
+1
> Gareth Reakes <[EMAIL PROTECTED]> writes:
>
>
> > Hey, here is my +1, but I don't know if we really need a
> > vote. I say that because the Xerces TLP does not even
have any
> > committers yet. We have a PMC (without a mailing list!!),
but
> >
> XercesDOMParser *parser = new XercesDOMParser;
> DOMTreeErrorReporter *errReporter = new DOMTreeErrorReporter ();
Do you really need to build a DOM tree?
> It seems that each call to event () is fairly expensive - running at
about 23 docs/sec
> on my system here at work
I can't give an opinio
> - Convert these files into actual templates, perhaps. I haven't
> looked enough into the implementations to know whether this is
> possible, or to discover what else might prevent us from doing this. I
> do know that we use templates elsewhere in Xerces, so this shouldn't
> break any com
> >And, also, Alberto, the VMware/gcc/x86 comment was downright nasty! I
> >bet Viet could get you a "discount" on SPARC/Forte(SunOne?); probably a
> >discount on training, too!
>
> I would have problems fitting it in my office ;-); but it would be nice
if
> Sun donated a bunch of Solaris hardw
> > The first of the two requirements is the killer, because it
> > essentially means that allocators cannot have instance data.
>
> I found an interesting discussion about that on comp.lang.c++:
> http://coding.derkeiler.com/Archive/C_CPP/comp.lang.cpp/2004-01/447index
.html
> where opinions go a
> from a xerces and xalan users point of view it is always a blocker
> for me that both libraries don't share a rich common code base.
Yes, it's unfortunate, because it would make many things much easier for
our users. On the other hand, you would not believe the number of posts
over the years
Hi Gareth,
> I should have read this mail before replying! It was certainly the
> case in the past the some of the platforms that xerces supported did
> not have decent STL support. Has this now changed? Dean knew all the
> issues if I recall correctly and does sometimes lurk on the list.
> Lots of cool ideas there. I'm with Alby though in being reticent about
> drawing in STL-based code at this juncture. I could be wrong about
this,
> but I seem to recall something about Xalan-C having relatively recently
> gone through a painful change away from STL for the sake of portabili
> Hi Alberto,
>
> According to my debuggin on VC7/WinXP, delete
> aTranscoder will invoke the global delete operator,
> which happen to work fine simply because the current
> memory manager implementation happen to use global new
> operator as well.
>
> If the memory manager implementation change
> Hi Joanne,
>
> As per your suggestion, I've used the compiling command, along with
> changing test.c (to remove include). I'm getting the compiler errors
> below. It looks like maybe a library issue...
>
> /tmp/ccSN4FhO.o(.text+0x17): In function `main':
> : undefined reference to `xercesc_2_
> The problem i have is that i need to parse a huge file
> that's why i decided to use the sax parser. however
> the file contains a particular encoding and the parser
> fails to transcode those strings. For example one line
> says Moléculaire
It's very very unlikely the parser cannot transcode d
> 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
> Discussions with my colleagues has raised a wish-list item. It would be
nice to have a "nested comment" feature
> allowing the commenting of large portions of XML, which itself may
contain comments.
You want something you think is "nice," but has a very high cost.
Something that would requir
> I am writing xml files which contain physical units.
> Some units contain the greek mucro.
Do you mean U+03BC which is "GREEK SMALL LETTER MU" or U+00B5, which is
"MICRO SIGN"? There is no Greek "mucro" character.
> Xerces writes it as two characters, I remember thats
> because it cannot be d
> Hi,
> I beginner with Xerces, can you show me a code that do this?
Look at the DOMPrint sample application.
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Alberto,
One problem I noticed with your fix is the call to resolveEntity() in the
various overloads of resolveSystemId() always result in a null pointer for
the public ID, meaning that any mechanism that relies on public IDs will
not work. For example, in IGXMLScanner.::resolveSystemId():
> I've been experimenting with using SAX2XMLReader::getSrcOffset()
> to find the file position that elements were found at. The problem
> with getSrcOffset() is that it doesn't always correspond exactly
> to the absolute file position, as (for example) XMLReader will
> sometimes silently eat the LF
> Is compatible binaries compiled for 64 bits with 32 bits platforms?
No.
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> I have a question regarding CData Section, say I have an element
> in XML defined as following:
>
>
>
>
>
> When I use the SAX parser in Xerces-c, I got the character data for the
element "Customer",
> is this the expected behavior?
Yes.
> I thought the data should be the whole thin
> >I've been building my own binaries for use with Xalan-C++ for months
> >without any issues.
> >
> >
> Are you also using Visual C++ .Net 2003? If so, is there anything
> different about your procedure?
We are using 2003, and there's no change in what we're doing. We just let
2003 translat
> The sequence of events has been something like this:
>
> I double-click on the VC7 project file for all.
>
> MSDev converts all the project file stuff to be 7.1 compatible.
So, you're using Visual C++ .Net 2003?
> I try to run DOMCount. A dialog comes up:
>
> "These project configurations
> Afaik, when overloading 'placement' new and delete
> like that, the only time the corresponding overload
> of delete will be called is if the constructor throws.
> All other times you have to call the destructor and
> the right version of delete yourself.
This is not true. If a class implements
Hi Graham,
> > All classes that derive from XMemory use "placement" new with a
> > MemoryManager instance, and the normal delete expression. The call
stack
> > you posted looks fine.
>
> But is this the correct behaviour? I think the destructor for the
> object should be called, then the op
> I'm seeing a crash when an IGXMLScanner held statically is destroyed.
> I'm using Xerces 2.3.0 on linux compiled with gcc 3.2.
Can you elaborate on what you mean by "held statically?" You shouldn't
have any static instance of Xerces-C classes, as they cannot be created
before the library is i
> But the reason for doing this is eloquently expressed
> in this very thread--people were confused by this
> library's presence, and some thought they needed it
> around to use the parser.
Are you sure that's what's being expressed? Because that's not how I read
it. I read it as "the distribut
> This was done intentionally. On no other platform
> were both debug and release binaries both issued,
> so it wasn't clear why this was being done on Windows.
> No functionality is lost.
Actually, functionality is lost, because you can no longer build debug
executables for your applications th
> The idea is to take advantade of the SAX and its ability to
> process a stream of non-specific length and combine that with
> the data organization of DOM.
I'm not sure I understand what you mean by this. Since the same
underlying scanner technology runs the SAX parsers and the DOM parsers and
> While the list is discussing the importance of adhering
> to standards, is there any hope of getting a few simple
> XML schema bugs fixed before the next release (e.g.
> xml:lang is unusable, anyType doesn't handle arbitrary
> ttributes)? Most of them don't even get an acknowledgement
> in the bu
> A preprocessing service is not a bad work around; and I
> do have sympathy for the notion of standards of compliance.
> Still, I see this problem (control characters) often enough
> that I question the XML standard and Xerces' compliance to it.
> XML Spy does not, though Microsoft's DOM parser do
> I think the blame belongs with your clients' authoring tools, which
> should help them produce well-formed documents. On the other hand, if
> you want to work around the presence of certain illegal characters, you
> could (as a service) translate them into character entities before
> handing the
> I have found an issue trying to get special characters to display
correctly in SAX and
> have gotten it down to a call to getCharDataOpts()within void
> IGXMLScanner::sendCharData(XMLBuffer& toSend). I have looked through
the
> documentation and on the website, but have not found a way to set
Hi James,
I might be able to help a bit, but have no access to a machine. I
remember at least a year ago asking for an account on an Apache Mac box,
but that didn't get anywhere. Is there some hardware available that we
can use? It would also help us keep up with Xalan-C's Mac port.
Thanks!
> I am writing a multi-threaded server to catch and process
> XML from multiple clients.
> I want to be able to create the validating parser up fromt
> and then clone it into each thread (one per connection), but
> I cannot seem to find a simple way to copy my parser once I
> have it built.
Ther
> My question is
>
> - Can we use xerces 1.4 on AIX 5.2 platform , which
> has been compiled using Visual Age 6.0 compiler
I don't think anyone can answer that question. You will simply have to try to build it from source, which you can download from here:
http://archive.apache.org/dist/xml/x
> The project is indeed in the directory indicated. Is there anything
> special that has to be done to get this to work? Does the project file
> need to be writable? (It's in a source control system).
Yes, because the scripts have to modify the project files for the selected
build options.
> Al
> Is it possible to use packageBinaries.pl to create a debug build of
> Xerces? Alternatively, if someone had directions for building with ICU
> in MSVC, then I could build in debug from within MSVC, but currently
> the only instructions for building ICU are using the perl scripts (the
> instructi
Hi Simon,
I reported such a bug earlier, although you may be seeing a different
issue. You might want to look at the latest CVS and see if you can
retrofit some patches for the scanners into 2.5.0. In particular, take a
look at src/xercesc/internal/IGXMLScanner2.cpp, at a patch in
IGXMLScanner::
> Why do all that? If XMLCh is not a typedef for wchar_t
> on your platform just cast the string to wchar_t*. Or am
> I missing some subtlety?
On some platforms wchar_t is a 32-bit integral, while on others it's a
16-bit integral, and there are very few platforms where wchar_t contains
Unicode cod
Hi,
This document is not encoded in UTF-8, so it is not well-formed. I tried
"ISO-8859-1" and it worked, but that's just a guess at the encoding. You
need to find out what the real encoding is.
Dave
-
To unsubscribe, e-mail:
Hi,
Text nodes do not have children. In your example, the "Child" node's
parent is "Parent", which is an Element node.
There are no RFCs to examine to figure this out -- just look at the DOM
recommendation:
http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-1590626202
Dave
|-+---
> Hi all, yeah, I'm a newbee here...
>
> Maybe I'm doing something wrong or maybe it's just Friday afternoon and I
want to go home,
> but I can't seem to find Xerces-C++ on the product list page to submit
this bug to Bugzilla.
> I see Xerces-J and Xerces-P but no Xerces-C. :-(
>
Xerces-C is using
Hi,
This is a known bug with Xerces-C 2.4. You should upgrade to 2.5 to get
the fix.
Dave
"Gary Hughes"
> > Xalan-C does not define or use the Xerces-C macros that
> > affect Xerces-C's class export macros. You should look very
> > carefully at what you did to build Xerces-C as a static
> > library and make sure have modified the following lines in
> > xercesc/util/Compilers/VCPPDefs.hpp:
> >
> >
>
>I'm using Windows XP search mechanism and can't find any of
them
> (dllimport keyword). :( Can you recommend some better tool?
>
> Thank you,
> Milan
Xalan-C does not define or use the Xerces-C macros that affect Xerces-C's
class export macros. You should look very carefully at wha
>[EMAIL PROTECTED] wrote:
>
>>>Although XMLCh is UTF-16, I believe the transcoding routines make a
>>>point of escaping reserved characters like "<" to "<", so the two
>>>string formats you mention are not interchangeable.
>>>
>>>
>>
>>Those characters are not escaped during transcoding. They woul
> Although XMLCh is UTF-16, I believe the transcoding routines make a
> point of escaping reserved characters like "<" to "<", so the two
> string formats you mention are not interchangeable.
Those characters are not escaped during transcoding. They would only be
escaped when generating markup.
"Bovy, Stephen J" <[EMAIL PROTECTED]> wrote:
> Then why haven't those fixes been merged back into the Xerces tree ???
You are assuming there are fixes. It may just be that there are tweaks
needed to new code which has appeared since the last time they did a port.
That typically happens with ports
> Can I do the following:
>
> class myinput : DOMInputSource, BinMemInputStream
> {
>
> public:
>
> myinput ( ) { };
>
> ~myinput ( ) { };
>
> BinInputStream* makestream ( ) { return this };
>
> }
You shouldn't do this, because the parser will want to delete the
BinMemInputStream instance, and
Hi,
This is the wrong list for this question. However, I'll respond, since the
answer is brief. The buffer is not null-terminated, so you need to check
the length of the stream, or add a terminating null.
In the future, please make sure you post to the correct list.
Thanks!
Dave
|-
Well, then you didn't read carefully enough:
http://www.w3.org/TR/REC-xml/#sec-line-ends
"To simplify the tasks of applications, the XML processor MUST behave as
if it normalized all line breaks in external parsed entities (including
the document entity) on input, before parsing, by tran
> hmm, can someone try this out ? the issue kind of frustrates my
progress...
If you're so frustrated, there are lots of XML resources out on the web.
How about just reading the XML recommendation?
http://www.w3.org/TR/REC-xml
> one of the tags in my source XML contains a CDATA section, with
Hi Gareth,
I was thinking that would be the thing to do, and it could be put somewhere
under ifdef, since basic_string is still not ubiquitous.
I might have some free time to give it a shot.
Dave
|-+>
| | Gareth Reakes
Hi Scott,
Yes, I wasn't implying that it would be easy, but it is possible to do, and
might be worthwhile, if you really want to use the functionality of
std::basic_string and you have multiple platforms to cover.
My experience has been that transcoding to the local code page is only an
answ
This is a FAQ:
http://xml.apache.org/xerces-c/faq-build.html#faq-13
You must be using the multithreaded DLL run-time library, or the Debug
multithreaded DLL run-time library, and you must link your program with the
appropriate release or debug Xerces library.
Dave
|-+--
Another possibility is for you to use a more modern STL, such as STLport.
Or, you can simply use std::vector instead of std::string. It doesn't give
you as much functionality as std::basic_string, but it's a start.
Xalan-C has a class called XalanDOMString that I wrote on top of
std::vector,
You don't transcode, which is what the problem is in the first place.
Dave
|-+--->
| | Sylvain Duval |
| | <[EMAIL PROTECTED]|
| | > |
| | |
| |
Using std::wstring is not very portable, because wchar_t may not be the
same as XMLCh. In fact, it will only be the same on a very few platforms.
Why not use std::basic_string instead, if your compiler's standard
library has templated string classes?
That way, you're still guaranteed interop
Take a look at the documentation regarding migrating to C++ namespaces:
http://xml.apache.org/xerces-c/migrate_archive.html
Dave
|-+--->
| | Nathan Smith|
| | <[EMAIL PROTECTED]|
| | xar.com>|
> I don't recall whether creating a parser on the stack is supported, but
you seem to have strong evidence that the answer is "no."
I create parsers on the stack all the time without problems.
Dave
-
To unsubscribe, e-mail:
Hi Joanne,
Yes, there is a Perl script available that runs under Cygwin. Look at
xml-xerces/c/scripts/packageBinaries.pl.
Dave
|-+--->
| | Joanne Bogart |
| | <[EMAIL PROTECTED]|
| | rd.edu> |
> That's what I was expecting. That's what worries me
>
> I don't do much in the events.
> I copy the pointer for element names and the string for text
> and a small bit of management to make sure there are no leaks or other
nastiness
> I am doing a progressive parse but I wouldn't have thought
> > that is what the parser does if validation is off/ there is no
> > reference to a DTD.
>
>
> Ok, and to enable this, do I call something like this:
>
> parser->setValidationScheme( AbstractDOMParser::Val_Always );
No, you don't need to do that. Checked that a document is well-for
Daniel,
Can you please turn off requesting a return receipt when you post to this
list!
Thanks!
Dave
|-+--->
| | "Gröndal Daniel"|
| ||
| | |
| | 03/16/2004 02:15|
Return Receipt
Your SV:Re: SV:HandlerBase problem with SAXXMLREADER reader
document
:
Return Receipt
Your SV:HandlerBase problem with SAXXMLREADER reader
document
:
Return Receipt
Your SAX2XMLReader and features?
document
:
OK, how about Google?
http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=zip%2Eexe
which leads to:
http://lists.wku.edu/pipermail/info-zip/2002-April/71.html
which leads to:
http://www.info-zip.org/pub/infozip/
All of which took about 20 seconds.
Dave
|--
Hi,
The mangled names suggest you have old objects or old header files in the
build, since the missing symbols are in the namespace "xercesc_2_2".
>From what I can see, this doesn't have anything to do with building the
Xerces-C library, although your email seemed to suggest the missing symbo
Hi,
This warning does not cause any unresolved symbol problems on HP. I get
the same warnings when I build, but have no problems linking and running
with Xerces-C 2.5.
If you posted a _small_ snippet of some of the unresolved symbols, someone
might be able to help, but you've not done that y
Hi Neil,
We build Xalan-C with that version of the compiler and we still see those
warnings. We compile with +p, which may explain why we get them, and
Xerces-C does not.
Dave
|-+--->
| | Neil Graham |
| | <[EMAIL PRO
I don't see any unresolved symbols, only warnings that the HP compiler does
not implement part of the C++ standard.
Dave
|-+--->
| | "Appaji, Prahalad P |
| | [ITS]" |
| | <[EM
You save all of the text in your own buffer, until you get an event that's
not characters().
I've never used progressive parsing, and there's no real standard, so
you'll have to experiment with it to see how it works.
Dave
Hi,
The parser will also make multiple calls to the characters function when it
encounters an entity reference, so your plan is likely unworkable. Also,
it's quite possible the buffer size could change in the future, or the
parser's behavior could change for some other reason.
Dave
Hi Endre,
You don't need to downcast. DOMNode::getNodeName() will return the target,
and DOMNode::getNodeValue() will return the data. If you want to downcast,
you can just use a static cast, after you've called DOMNode::getNodeType()
and verified it's a processing instruction.
Dave
Hi,
Translating to the local code page is a very bad application design. You
should transcode to UTF-8 instead, since you will be guaranteed that all
characters can be represented. Probably what's happening is some
characters are not representable in the local code page, and
XMLString::trans
Have you called the static initialization routine?
See XMLPlatformUtils::Initialize() and XMLPlatformUtils::Terminate() for
more information. This is well documented.
Dave
The options you see being used are for the HP compiler, not for gcc. I
don't think anyone has ever ported Xerces to the gcc compiler on HP-UX.
Dave
> Actually I had already read that and found it to be somewhat ambiguous.
>
> Method: Append Child
> Adds the node newChild to the end of the list of children of this node.
If
> the newChild is already in the tree, it is first removed.
> Parameters:
> newChild of type Node
> The node to a
> Don't everybody answer at once ;-)
>
> I apologize if this question is obvious or inappropriate, but it is a
> behavior of the parser that I haven't been able to definitively classify
> yet. So, if anyone could offer any help I would really appreciate it.
The DOM recommendation will answer
on never caught any exceptions. and the crash actually happens
inside the parser code and not my application. I thought there might be
some sort of flags that I could set so that the parser could throw
exceptions in cases such as this.
Regards,
Xuefu
Are you catching the appropriate exceptions? If not, your application will
crash. See the sample applications and the documentation for more
information.
Dave
> On Fri, Oct 17, 2003 at 10:11:48AM -0700, [EMAIL PROTECTED]
wrote:
> > > The XMemory class uses a global memory manager class thet defaults to
> > > MemoryManagerImpl. This latter is in charge of allocating and freeing
> > > memory and will return a pointer to that memory to XMemory. XMemory
Hi Adam,
You might want to do a search of the mailing list archives, because I
remember a previous discussion about this and it related to how XML schema
specifies Base64 should work:
http://marc.theaimsgroup.com/?l=xerces-c-dev&w=2&r=1&s=base64&q=b
This may or may not be relevant...
Dav
> The XMemory class uses a global memory manager class thet defaults to
> MemoryManagerImpl. This latter is in charge of allocating and freeing
memory
> and will return a pointer to that memory to XMemory. XMemory does some
> management of its own, however, "aligning" the pointer it returns by
>try
>{
>SAX2PrintHandlers handler(encodingName, unRepFlags,
expandNamespaces);
>parser->setContentHandler(&handler);
>parser->setErrorHandler(&handler);
>//parser->parse(xmlFile);
>//errorCount = parser->getErrorCount();
>}
>
>catch (cons
Hi Gareth,
A better solution would be make XMLString::replicate() a non-inline
function. Too many people already are confused by XMLString::transcode(),
etc., and I worry that an exception like this will just create more
confusion. It would great if people actually read the documentation bef
Hi all,
I think the problem is that XMLString::replicate() is inline, so the memory
will come from the heap of the particular module that's making the call.
The defeats the purpose of having XMLString::release().
Dave
Hi Sean,
> Problem being that, according to the standard, 'this' isn't required to
be
> a valid pointer until the body of the constructor has been entered. A
fix
> would likely require adding a new protected method to the parent class to
> pass the pointer.
Can you provide a reference to the
1 - 100 of 235 matches
Mail list logo
