Ok I see too many messages reguarding it hey my mbox!! ;-P
// DOMSave.h
//
//
#ifndef DOMSAVE_H
#define DOMSAVE_H
// Includes
#include
#include
#include
#include
#include
#include
#include
#include
#include
#incl
Title: Message
> A xerces build with the option to
use ICU converters triggers a full ICU build as part of the xerces build, so we
wont be able to use that option from within an ICU build.
I know I already wrote about this but let me say it again. I
submitted a patch to Xerces 1.3 to not
Would be nice to bulish your file serialization code throgh this forum .
> --
> From: Anthony Zawacki
> Reply To: [EMAIL PROTECTED]
> Sent: Thursday, July 12, 2001 12:13 AM
> To: [EMAIL PROTECTED]
> Subject: Re: problem regarding DOMPrint
>
> Hello,
>
> Your
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2588
*** shadow/2588 Wed Jul 11 21:45:14 2001
--- shadow/2588.tmp.16910 Wed Jul 11 21:45:14 2001
***
*** 0
--- 1,18
+ ++
+ | new version of xer
"Dave Connet" <[EMAIL PROTECTED]> writes:
> I guess I don't really see the problem. Subdirectory namespaces
> really don't matter - it's the header files themselves. And if you
> have 2 headers with the same name and you need both, you're pretty
> much in trouble anyways because of things like "#
It's pretty easy to make it clear about includes with comments:
// Here's the xerces includes
#include ...
// Here's the abc includes
...
I guess I don't really see the problem. Subdirectory namespaces really don't
matter - it's the header files themselves. And if
> -Original Message-
> From: Nick Denning [mailto:[EMAIL PROTECTED]]
>
>
> Excellent idea, and I would be happy with 1.6
>
> Nick
I prefer 1.5.1, but 1.6 would be fine for me. I'm +1 for the whole concept
of a new release; but the name itself is a side issue. I'd rather defer the
decision
I have seen the others responses, and as I am fiddling around with DOMPrint
at the moment, let me show you what I have done and see if that does the
trick for you.
//
---
// Local classes
//
Just an observation, but it has taken me some time to resolve this. I think
this is also a fairly common problem with many other people failing to
handle the escape characters (and not even knowing about them).
Is there any reason why the DOMPrint example does not convert all the
standard escape
Excellent idea, and I would be happy with 1.6
Nick
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: 11 July 2001 15:57
To: [EMAIL PROTECTED]
Subject: Build a Xerces 1.5.1 or Xerces 1.6?
Hi,
As more and more users are reporting that ElemStack memory leak in
Xerces 1.5
>How do you prematurely end parsing, using the parse() method of the SAX
parser,
>without using the progressive parsing methods like parseNext(). Can you?
Throw an exception from your handler. That really is the standard solution.
If you throw a recognizable exception, the routine which invoked
Hello
Do I have to upgradde to xerces-c-1_5 or xml4c1.5 . I am kine of confused
by the the last two mails
Thanks
Aniruddha
-Original Message-
From: Herb Chong [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 2:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem building xerces-
Throw an exception from within your document handler when it is time to
prematurely end the parse.
-Original Message-
From: Williamson, Siehnai
To: '[EMAIL PROTECTED]'
Sent: 7/11/01 3:45 PM
Subject: Stopping in the middle of a parse
Hi,
How do you prematurely end parsing, using the
so long as you are using the VAC++ 5.0 compiler, you will have all kinds of
problems until you path the code yourself or you update to XML4C 1.5.
Herb...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-m
Hello,
Your not doing anything wrong, and there is not any problem (depending on
your perspective.)
If youlook at the DOMPrint example, you will see that it ignores the
ostream it recieves, and uses a formatter in it's place that always output
to std::out. You will need to change and fix this t
Title: Stopping in the middle of a parse
Hi,
How do you prematurely end parsing, using the parse() method of the SAX parser, without using the progressive parsing methods like parseNext(). Can you?
Siehnai Williamson
DocuCorp International, Inc.
1.4 has no support for VAC++ 5.0. you have to update to 1.5 unless you are
willing to make the changes to support the newer compiler.
Herb
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Do you guys need help porting the rest of the Schema? I may have some time
on my hands in the near future... You is handling that?
Jim
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 1:29 PM
> To: [EMAIL PROTECTED]
> Subject: Re
When I try to build xerces-c-1_4 on AIX 4.3.2 I get the following problem
ld: 0711-224 WARNING: Duplicate symbol:
TranscodingException::TranscodingException(const TranscodingException&)
ld: 0711-224 WARNING: Duplicate symbol:
XMLDeleterFor::XMLDeleterFor(XMLMutex* const)
ld: 0711-224 WARNING: Du
...snip...
> ofstream outputfile;
> outputfile.open("/tilde/lpcoop/temp.txt",ios::out);
what do you expect this line to do?
> outputfile << doc << endl;
> outputfile.close();
>
> Please tell me what the problem is ?? If i try to write a
> normal string to
> the outputfile like outputfile <<
I'm all for a maintenance release. I'm vaguely fearful about the
implications of leaving the DLL name the same, in that you'll have to
inspect the timestamp to know which version you've got. But the whole issue
of naming is irrelevant to me, since I build my own static library. Maybe
those who use
Two thumbs up for Xerces 1.5.1
Thanks!
Dave
Tinny Ng
<[EMAIL PROTECTED]To:
Has anyone done any work on parsing a DTD? Before parsing an XML file, I need to
store the DTD into the database.
TIA,
Drew Tennenbaum
**
This email and any files transmitted with it are confidential and
intended solely for
We're using xerces-c compiled with cc 4.2 on Solaris 2.6, but it doesn't
work the code that uses the library is the following:
try
{
XMLPlatformUtils::Initialize();
}
catch (const XMLException& toCatch)
{
//cout << "Error during initialization! :\n"
"Tinny Ng" <[EMAIL PROTECTED]> writes:
> Since it's only a month since Xerces 1.5, not too many new code has been
> added. So instead of Xerces 1.6, may be we can name it Xerces 1.5.1
> which means the dll name will remain as libxerces-c1_5.so .
why can't it be libxerces-c1_5_1.so?
Irregardles
Hello
When I try to build xerces-c-1_4 on AIX 4.3.2 I get the
following error several times
/usr/vacpp/bin/xlC_r -qnotempinc -D_THREAD_SAFE -c -O
-DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELO
ADER -DXML_USE_NETACCESSOR_SOCKET
-I/home/ashevade/devlopment/server/soapengine/soapxmlparse
Hi ,
I am trying to work with the example DOMPrint given in the samples
directory. The problem that I am haiving is that ... I am trying to print
out the output in a FILE insted of printing it out on the CONSOLE. I am
opening and closing the file properly but the output prints out on the
CONSOLE a
1.5.1 is psychologically more acceptable to managment when absorbing
changes.
Herb...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I totally agree - 1.6 works for us and we'd love to get the new bits.
Jim
> -Original Message-
> From: Tinny Ng [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 10:57 AM
> To: [EMAIL PROTECTED]
> Subject: Build a Xerces 1.5.1 or Xerces 1.6?
>
>
> Hi,
>
> As more and more use
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2565
*** shadow/2565 Wed Jul 11 00:46:16 2001
--- shadow/2565.tmp.10617 Wed Jul 11 09:41:37 2001
***
*** 2,9
| The external subset can be empty (Section 2.8) |
+---
This is going to get loads of responses
In the circumstances 1.5.1 sounds ok to me!
Chris Prior
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: 11 July 2001 15:57
To: [EMAIL PROTECTED]
Subject: Build a Xerces 1.5.1 or Xerces 1.6?
Hi,
As more and more users are
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2561
*** shadow/2561 Tue Jul 10 23:55:06 2001
--- shadow/2561.tmp.10401 Wed Jul 11 09:05:46 2001
***
*** 2,9
| Problem with standalone documents |
+---
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2562
*** shadow/2562 Wed Jul 11 00:07:35 2001
--- shadow/2562.tmp.10336 Wed Jul 11 08:58:23 2001
***
*** 2,9
| Fixed Attribute Default validity constraint validation failed |
+---
"john guildesh" <[EMAIL PROTECTED]> writes:
> A customer of mine ordered me to develop a program to handle XML
> files, and I want to use Xerces-C libraries.
>
> Wich concepts could I receive money for?
>
> Must I mention Apache Project?
>From LICENSE.txt:
* Redistribution and use in source
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2564
*** shadow/2564 Wed Jul 11 00:30:09 2001
--- shadow/2564.tmp.10293 Wed Jul 11 08:51:25 2001
***
*** 25,28
]>
It is written in English
!
--- 25,51
]>
It is written in English
!
!
! --- Add
Hi,
As more and more users are reporting that ElemStack memory leak in
Xerces 1.5, plus a number of other bugs reported lately, I am thinking
seriously we should get another build out to replace Xerces 1.5.
Since it's only a month since Xerces 1.5, not too many new code has been
added. So inst
Nick,
Yes I think that's the same problem ...
Tinny
Nick Denning wrote:
> Dear People,
>
> I have just joined the mailing list to enquire on a problem I think I have
> with the XERCES-C 1.5 parser which I think has a memory leak. I have
> checked the obvious things, having been a Xerces progr
Hi, Aniruddha.
>Looks like it was a problem with mangling , I had to change the definition
>in SunCCDefs.cpp to extern "C" stricmp(..) etc. So is this the a known
>issue or abug.
>Anyway I am very thankful for all your help.
I'm glad we solved this. I think it's a bug, as I have not heard
a re
Hi again!
A customer of mine ordered me to develop a program to handle XML files, and I want to
use Xerces-C libraries.
Wich concepts could I receive money for?
Must I mention Apache Project?
Thank you very much.
___
Get
Murray,
> To fix this, I'd like to add the 'xercesc/' bit to the includes in all
> the xerces-c header. BUT, then xerces-c wouldn't build because the
> headers are actually in src. SO, let's rename that directory. This
> technique is used by lots of libraries, such as gtk.
Sorry I couldn't quite
Peter,
Understand your point, but will not most people be using the run time
version, where its the include directory, and anyway do not people have to
modify the directory anyway when a new version is delivered?
Nick
-Original Message-
From: Peter A. Volchek [mailto:[EMAIL PROTECTED]]
"Peter A. Volchek" wrote:
>
> > Here's my previous post again, for those who missed the reasoning:
> >
> > Murray Cumming wrote:
> > >
> > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
> > >
> > > I recently changed the build files so that they install the headers
> > > under
"Murray Cumming" <[EMAIL PROTECTED]> writes:
> "Jason E. Stewart" wrote:
> >
> > "Peter A. Volchek" <[EMAIL PROTECTED]> writes:
> >
> > > > > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
> > >
> > >
> > >
> > >
> > > Don't do that Have you thought about thousand
> >
> Here's my previous post again, for those who missed the reasoning:
>
> Murray Cumming wrote:
> >
> > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
> >
> > I recently changed the build files so that they install the headers
> > under a /include/xercesc directory instead of poll
Here's my previous post again, for those who missed the reasoning:
Murray Cumming wrote:
>
> I'd like to rename the 'src' directory to 'xercesc'. Here's why:
>
> I recently changed the build files so that they install the headers
> under a /include/xercesc directory instead of polluting
> had
> > > > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
> >
> >
> >
> >
> > Don't do that
> > Have you thought about thousand customers/developers who will have to
modify
> > their working projects, documentations and so on.
>
> Certainly an issue, but is it an over-riding
"Jason E. Stewart" wrote:
>
> "Peter A. Volchek" <[EMAIL PROTECTED]> writes:
>
> > > > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
> >
> >
> >
> >
> > Don't do that
> > Have you thought about thousand customers/developers who will have to modify
> > their working proj
"Peter A. Volchek" <[EMAIL PROTECTED]> writes:
> > > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
>
>
>
>
> Don't do that
> Have you thought about thousand customers/developers who will have to modify
> their working projects, documentations and so on.
Certainly an
"Peter A. Volchek" wrote:
>
> > > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
>
>
>
> Don't do that
> Have you thought about thousand customers/developers who will have to modify
> their working projects, documentations and so on.
Yes, but I think that the change wi
> > > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
Don't do that
Have you thought about thousand customers/developers who will have to modify
their working projects, documentations and so on.
Peter A. Volchek
Software Engineer
Metis International, Inc.
[EMAIL PROTECTE
"Murray Cumming" <[EMAIL PROTECTED]> writes:
> Murray Cumming wrote:
> >
> > I'd like to rename the 'src' directory to 'xercesc'. Here's why:
>
> Can I have a maintainer's yes/no about this, please?
Already gave my +1
jas. (xerces-p maintainer)
---
Murray Cumming wrote:
>
> I'd like to rename the 'src' directory to 'xercesc'. Here's why:
>
> I recently changed the build files so that they install the headers
> under a /include/xercesc directory instead of polluting
> had a secondary aim - to make it more obvious when client code #includes
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2565
*** shadow/2565 Wed Jul 11 00:46:16 2001
--- shadow/2565.tmp.6305Wed Jul 11 00:46:16 2001
***
*** 0
--- 1,26
+ ++
+ | The external subse
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2564
*** shadow/2564 Wed Jul 11 00:30:09 2001
--- shadow/2564.tmp.6269Wed Jul 11 00:30:09 2001
***
*** 0
--- 1,28
+ ++
+ | Valid XML doc with
54 matches
Mail list logo
