You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by kiuma <ki...@usa.net> on 2001/06/04 13:54:09 UTC
Borland users good news!!!!
Ok, I'v just compiled Xerces cvs with BCB4 and it seems to work
(encoding included ;-) )!
The project 4 bcb4 in the cvs tree is buggy so i'll send to apache web site
both modified sources and binaries; wait 1 or 2 days for a preliminary
debug!.
I need some1 (i.e. xerces-c developer) to send code and dll and lib.
cya,
kiuma.
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: wrapping the Xerces parser !!
Posted by Dean Roddey <dr...@charmedquark.com>.
Since you could just effectively rip off the existing one, probably so.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
droddey@charmedquark.com
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
----- Original Message -----
From: "anand awasthi" <on...@yahoo.com>
To: <xe...@xml.apache.org>
Sent: Monday, June 04, 2001 11:49 AM
Subject: Re: wrapping the Xerces parser !!
> thanks a lot for suggesting better options...
>
> i guess i forgot to mention the time frame,
> i got only a week to do this.
> is 1 week sufficient enough time for coding on DOM
> Parser front ??
>
> thanks
>
>
>
>
> yeah
> --- Dean Roddey <dr...@charmedquark.com> wrote:
> > You might want to just consider writing your own
> > DOMParsre and SAXParser. If
> > you look inside them, they aren't very complicated.
> > And doing so will let
> > you provide your own interfaces without paying the
> > extra performance cost of
> > going through a middel parser layer. You'd just wire
> > the scanner directly to
> > your interface, just like DOM/SAXParser does.
> >
> > --------------------------
> > Dean Roddey
> > The CIDLib C++ Frameworks
> > Charmed Quark Software
> > droddey@charmedquark.com
> > http://www.charmedquark.com
> >
> > "Why put off until tomorrow what you can
> > put off until the day after tomorrow?"
> >
> > ----- Original Message -----
> > From: "anand awasthi" <on...@yahoo.com>
> > To: <xe...@xml.apache.org>
> > Sent: Monday, June 04, 2001 11:25 AM
> > Subject: wrapping the Xerces parser !!
> >
> >
> > > Hi,.
> > >
> > > I am making an XML ADATPER which will parser
> > incoming
> > > client XML file/generate DOM and convert DOM to
> > XMLs
> > > ans send them to clients.
> > >
> > > I am using Xerces parser, but i dont want my
> > client to
> > >
> > > interact with Xerces implementation directly. so i
> > > want to wrap the Xerces implementation within my
> > api.
> > > To do this, i am planning to extend the Xerces
> > DOM/SAX
> > > APIs and then ask the clients to use my own APIs
> > > inplace of Xerces,
> > >
> > > e.g.
> > >
> > > XML_DOM_Document : DOM_Document
> > > ( where XML_DOM_Document is my class and
> > DOM_Document
> > > is Xerces impelmentation).
> > >
> > > later my clients will call methods on
> > XML_DOM_Document
> > > instance.
> > >
> > > e.g.
> > >
> > > XML_DOM_Document xmldoc ;
> > > xmldoc.getDocumentType();
> > >
> > > is this inheritance approach good or do you
> > suggest
> > > any better mechanism to wrap Xerces implementation
> > in
> > > some other way ??
> > >
> > > pls enlighten me
> > > thanks
> > > Oni
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Get personalized email addresses from Yahoo! Mail
> > - only $35
> > > a year! http://personal.mail.yahoo.com/
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > xerces-c-dev-unsubscribe@xml.apache.org
> > > For additional commands, e-mail:
> > xerces-c-dev-help@xml.apache.org
> > >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > xerces-c-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail:
> > xerces-c-dev-help@xml.apache.org
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: wrapping the Xerces parser !!
Posted by anand awasthi <on...@yahoo.com>.
thanks a lot for suggesting better options...
i guess i forgot to mention the time frame,
i got only a week to do this.
is 1 week sufficient enough time for coding on DOM
Parser front ??
thanks
yeah
--- Dean Roddey <dr...@charmedquark.com> wrote:
> You might want to just consider writing your own
> DOMParsre and SAXParser. If
> you look inside them, they aren't very complicated.
> And doing so will let
> you provide your own interfaces without paying the
> extra performance cost of
> going through a middel parser layer. You'd just wire
> the scanner directly to
> your interface, just like DOM/SAXParser does.
>
> --------------------------
> Dean Roddey
> The CIDLib C++ Frameworks
> Charmed Quark Software
> droddey@charmedquark.com
> http://www.charmedquark.com
>
> "Why put off until tomorrow what you can
> put off until the day after tomorrow?"
>
> ----- Original Message -----
> From: "anand awasthi" <on...@yahoo.com>
> To: <xe...@xml.apache.org>
> Sent: Monday, June 04, 2001 11:25 AM
> Subject: wrapping the Xerces parser !!
>
>
> > Hi,.
> >
> > I am making an XML ADATPER which will parser
> incoming
> > client XML file/generate DOM and convert DOM to
> XMLs
> > ans send them to clients.
> >
> > I am using Xerces parser, but i dont want my
> client to
> >
> > interact with Xerces implementation directly. so i
> > want to wrap the Xerces implementation within my
> api.
> > To do this, i am planning to extend the Xerces
> DOM/SAX
> > APIs and then ask the clients to use my own APIs
> > inplace of Xerces,
> >
> > e.g.
> >
> > XML_DOM_Document : DOM_Document
> > ( where XML_DOM_Document is my class and
> DOM_Document
> > is Xerces impelmentation).
> >
> > later my clients will call methods on
> XML_DOM_Document
> > instance.
> >
> > e.g.
> >
> > XML_DOM_Document xmldoc ;
> > xmldoc.getDocumentType();
> >
> > is this inheritance approach good or do you
> suggest
> > any better mechanism to wrap Xerces implementation
> in
> > some other way ??
> >
> > pls enlighten me
> > thanks
> > Oni
> >
> >
> >
> >
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Get personalized email addresses from Yahoo! Mail
> - only $35
> > a year! http://personal.mail.yahoo.com/
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> xerces-c-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail:
> xerces-c-dev-help@xml.apache.org
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail:
> xerces-c-dev-help@xml.apache.org
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: wrapping the Xerces parser !!
Posted by Dean Roddey <dr...@charmedquark.com>.
You might want to just consider writing your own DOMParsre and SAXParser. If
you look inside them, they aren't very complicated. And doing so will let
you provide your own interfaces without paying the extra performance cost of
going through a middel parser layer. You'd just wire the scanner directly to
your interface, just like DOM/SAXParser does.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
droddey@charmedquark.com
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
----- Original Message -----
From: "anand awasthi" <on...@yahoo.com>
To: <xe...@xml.apache.org>
Sent: Monday, June 04, 2001 11:25 AM
Subject: wrapping the Xerces parser !!
> Hi,.
>
> I am making an XML ADATPER which will parser incoming
> client XML file/generate DOM and convert DOM to XMLs
> ans send them to clients.
>
> I am using Xerces parser, but i dont want my client to
>
> interact with Xerces implementation directly. so i
> want to wrap the Xerces implementation within my api.
> To do this, i am planning to extend the Xerces DOM/SAX
> APIs and then ask the clients to use my own APIs
> inplace of Xerces,
>
> e.g.
>
> XML_DOM_Document : DOM_Document
> ( where XML_DOM_Document is my class and DOM_Document
> is Xerces impelmentation).
>
> later my clients will call methods on XML_DOM_Document
> instance.
>
> e.g.
>
> XML_DOM_Document xmldoc ;
> xmldoc.getDocumentType();
>
> is this inheritance approach good or do you suggest
> any better mechanism to wrap Xerces implementation in
> some other way ??
>
> pls enlighten me
> thanks
> Oni
>
>
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
wrapping the Xerces parser !!
Posted by anand awasthi <on...@yahoo.com>.
Hi,.
I am making an XML ADATPER which will parser incoming
client XML file/generate DOM and convert DOM to XMLs
ans send them to clients.
I am using Xerces parser, but i dont want my client to
interact with Xerces implementation directly. so i
want to wrap the Xerces implementation within my api.
To do this, i am planning to extend the Xerces DOM/SAX
APIs and then ask the clients to use my own APIs
inplace of Xerces,
e.g.
XML_DOM_Document : DOM_Document
( where XML_DOM_Document is my class and DOM_Document
is Xerces impelmentation).
later my clients will call methods on XML_DOM_Document
instance.
e.g.
XML_DOM_Document xmldoc ;
xmldoc.getDocumentType();
is this inheritance approach good or do you suggest
any better mechanism to wrap Xerces implementation in
some other way ??
pls enlighten me
thanks
Oni
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org