I just re-ran a compile link job, (that used to work)
but now all of a sudden I am getting unresolved refferences:
IEW2456E 9207 SYMBOL TRANSCOD UNRESOLVED.
IEW2456E 9207 SYMBOL LOADDOME UNRESOLVED.
IEW2456E 9207 SYMBOL @ST00574 UNRESOLVED.
IEW2456E 9207 SYMBOL @ST00575 UNRESOLVED.
IEW2456E
He wants to change the OUTPUT encoding
What does he mean by OUTPUT, is he talking about the OUTPUT from creating a NEW
DOCUMENT ???
-Original Message-
From: Jeroen N. Witmond [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 12, 2005 11:19 AM
To: xerces-c-dev@xml.apache.org
Subj
Sean Kelly seems to have a lot to say on this topic, maybee he can help
you write it
-Original Message-
From: Scott Cantor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 06, 2004 7:20 AM
To: [EMAIL PROTECTED]
Subject: RE: XMLCh vs wchar_t
> We asked this last time this conversat
"c version of xerces" there was no "wstring" in "c" can there
be anything more obvious than that ???
Or "wstring" was not a cross-platform construct
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Giampiero Gabbiani
Sent: Monday, October 04, 2004 3:
I would like to find a simple xsl template to convert something like
this:
Steve Bovy
9301 Pali Ave
818-352-9917
1234
-1
-15.41
-45.32
after running configure,
export _CXX_CXXSUFFIX=cpp
gmake
Regards,
David A. Cargill
"Bovy, Stephen J"
<[EMAIL PROTECTED]
com>
To
<[EMAIL PROTECTED]>
04/28/2004
e that IBM XML Toolkit support does).
Content-Type: text/plain;
charset="us-ascii" Subject:
z/OS and OS/390 runConfigure ??? Date: Tue, 27 Apr 2004 13:42:59 -0400 From: Bovy, Stephen J <[EMAIL PROTECTED]>
How come the runConfigure script has no support for z/OS and/or
OS/390
How come the runConfigure script has no support for z/OS and/or OS/390
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
lized xerces? There is a sample that does what
you are trying to do here (MemParse). Worth taking a look there.
Gareth
On Thu, 22 Apr 2004, Bovy, Stephen J wrote:
> I have the following code which I am using with
>
> the IBM toolkit 1.6 which is xerces 2.2
>
> MemBufInputS
I have the following code which I am using with
the IBM toolkit 1.6 which is xerces 2.2
MemBufInputSource* memBufIS = NULL;
Wrapper4InputSource* domBufIS = NULL;
memBufIS = new MemBufInputSource
(
(const XMLByt
You are right, here is the correct approach:
Thanks for the feedback, I realized though that I was doing the wrong
thing:
Here is the correct approach:
MemBufInputSource* memBufIS = NULL;
Wrapper4InputSource* domBufIS = NULL;
memBufIS = new MemBufInputSource
(
g what you are trying to achieve it is hard to
know if this is the best way to do it, however, the code looks OK to me.
Gareth
On Wed, 21 Apr 2004, Bovy, Stephen J wrote:
> How can I use DOMInputSource so that it uses a BinInputStream
>
> Any suggestions would be greatly appre
How can I use DOMInputSource so that it uses a BinInputStream
Any suggestions would be greatly appreciated
Can I do the following:
class myinput : DOMInputSource, BinMemInputStream
{
public:
myinput ( ) { };
~myinput ( ) { };
BinInputStream* makestream ( ) { return this };
}
---
I am trying to write some flexable code that can
either do a file parse or an in memory parse, but I am getting a
compile error on : doc = sstate->doc =
sstate->parser->parse(*memBufIS);
See below:
**
if ( sfile.ipc ) {
-Original Message-
From: Gareth Reakes [mailto:[EMAIL PROTECTED] On
Behalf Of Gareth Reakes
Sent: Wednesday, April 07, 2004 12:17 PM
To: [EMAIL PROTECTED]
Subject: Re: DOMWriter Questions
Hi,
> DOMImplementation *impl =
> DOMImplementationRegistry::getDOMImplementation(XMLString::trans
ndler.getSawErrors()
But, you ask some very good questions (which I agree deserve an answer )
-Original Message-
From: Nick Bastin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004 4:44 PM
To: [EMAIL PROTECTED]
Subject: Re: Parser not failing on bad schema?
On Apr 6, 2004, at 6:08 PM, B
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 on b
Message-
From: Bovy, Stephen J [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 4:05 PM
To: [EMAIL PROTECTED]
Subject: RE: Question
You need to do it on the parser before you do the parse:
parser->setFeature ( XMLUni::fgDOMNamespaces, true );
-Original Message-
From: Raj
You need to do it on the parser before you do the parse:
parser->setFeature ( XMLUni::fgDOMNamespaces, true );
-Original Message-
From: Rajesh Chilambi [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 1:02 PM
To: [EMAIL PROTECTED]
Subject: RE: Question
Hi,
Thanx for the reply
He did that with this:
domParser->setDoNamespaces(true);
Or is there more to it than that
-Original Message-
From: Gareth Reakes [mailto:[EMAIL PROTECTED] On
Behalf Of Gareth Reakes
Sent: Thursday, March 25, 2004 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Question
Hi,
you
>>if you got the document from the parser then you need to adopt it if
you want to release it, otherwise the parser will do >>it for you.
Ahhh there is my answer !!! Thanks !!!
BTW what is "adopting a document" all about, I've never heard of that
concept, of course I am new to all
this stuff ,
How do you delete/release and or free the dom
object tree when you are done with it..
I tried dom->release() but I got a nasty 0C4 abend
with the following trace:
The system detected a protection exception (System Completion Code=0C4).
>From entry point xercesc_2_2::AbstractDOMParser::~Abstrac
Xerces is a spaghetti code of intermixed and overlapping
"dependencies"...
It seems that c++ coders don't care about modularity, everything calls
everything else.
I did a "port" of Xerces, to sas/c on os/390 and had to link statically,
because
sas/c does not have a good DLL architecture, and I d
Hi List, I am new to xml and new to this list
Question # 1:
I have been struggling with an Idea.
Is there any way possible to create an xml document that
includes/im-beds its own schema within the doc, so that
I don't need to have two separate files. I was toying with the
idea of using "xpo
24 matches
Mail list logo
