The following issue has been updated:
Updater: Jeroen N. Witmond (mailto:[EMAIL PROTECTED])
Date: Thu, 13 May 2004 3:04 PM
Comment:
Detailed description of the patch.
Changes:
Attachment changed to jira_XERCESC-1211_Errors_and_warnings.txt
--
The following issue has been updated:
Updater: Jeroen N. Witmond (mailto:[EMAIL PROTECTED])
Date: Thu, 13 May 2004 3:03 PM
Comment:
Patch to solve a large number of these problems. Detailed description of the patch
will follow.
Changes:
Attachment changed to jira_X
Hi,
looking at the code I cannot see how this could happen (famous
last words). Do you have a minimal code snippet and XML document with
which I could try this?
Gareth
On Thu, 13 May 2004, Hassink, Brian wrote:
> Greetings,
>
> I'm finding that the document returned by AbstractDOMParser
The following comment has been added to this issue:
Author: Dan Rosen
Created: Thu, 13 May 2004 10:48 AM
Body:
Hi Neil,
Thanks for the advice ...
> On the other hand, if you can design a handler that knows how to
> make appropriate calls to the scanner's sendChars() method so that
The following comment has been added to this issue:
Author: Robert Buck
Created: Thu, 13 May 2004 10:36 AM
Body:
I can do that as well, if I can only find on Sun's site where they would take bug
reports on fdlibm, and convince them to make the change.
Since fdlibm has a greater i
The following comment has been added to this issue:
Author: David Bertoni
Created: Thu, 13 May 2004 10:16 AM
Body:
I hope you've also filed the same request with the developers of that library. After
all, it's that library which is at fault, and UNKNOWN could conflict libraries o
Hi Dave,
> Are you building a debug configuration?
No.
> Did
> you dump the symbols from the Xerces-C library you built to
> see if these missing symbols are defined?
How can I do that? I have one Borland tool (tdump) that do that, but it
works only with .dll files and not with .lib files.
Tha
The following comment has been added to this issue:
Author: Robert Buck
Created: Thu, 13 May 2004 9:55 AM
Body:
Yes, but namespaces is not at issue - the C preprocessor is. The issue specifically is
that many C libraries use #define. This particular one (fdlibm) does the following
> > 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:
> >
> >
The following comment has been added to this issue:
Author: Jesse Pelton
Created: Thu, 13 May 2004 9:45 AM
Body:
Does your compiler support C++ namespaces? Namespaces are designed to address
precisely this issue, and Xerces provides tools that you should be able to use to
resolv
> 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:
>
>#define
>
>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
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
> -Original Message-
> From: Alberto Massari [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 13, 2004 5:53 PM
> To: [EMAIL PROTECTED]
>
Hi Milan,
The symbols all have __declspec(dllimport), but you are now building static
libraries, that don't have that in the signature. Can you check your Xalan
sources to find out which macro is associated with that directive and make
it empty.
Alberto
At 17.47 13/05/2004 +0200, Milan Tomic
I've tried to link Xalan as static lib, but I got 11 linker errors
(unresolved externals). Linker can't find 11 Xerces
constructors/destructors, that Xalan is using. I'm using Xerces 2.5 with
Xalan 1.6. Does anyone have any idea why this happen? There have to be
some solution... maybe something wi
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1212
Here is an overview of the issue:
-
Greetings,
I'm finding that the document returned by AbstractDOMParser::adoptDocument() is
different than the one returned by AbstractDOMParser::getDocument() in that whitespace
text nodes appear to be inserted after non-whitespace text nodes in the former.
Has anyone else noticed this? Is it a
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1211
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Neil Graham
Created: Thu, 13 May 2004 6:45 AM
Body:
Hi Dan. A few thoughts: You might want to look at the way the
http://apache.org/xml/properties/input-buffer-size property is implemented in
Xerces-J, since that seems
Hi Greg,
This would be a bug. As you'll have noticed, a Jira bug entry has already
been opened.
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
The following comment has been added to this issue:
Author: Lénaïc Huard
Created: Thu, 13 May 2004 2:52 AM
Body:
I have the same problem when trying to build xerces 2.5.0 on this config :
% uname -a
SunOS 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Fire
% gcc -v
Reading specs
Yes we have done the same thing with Xalan. I can't remember the details
anymore but it is very similar to the Xerces conversion.
Good luck
/ Erik
> -Original Message-
> From: Milan Tomic [mailto:[EMAIL PROTECTED]
> Sent: den 12 maj 2004 16:13
> To: [EMAIL PROTECTED]
> Subject: RE: Linkin
22 matches
Mail list logo
