Urs,

I think this is fixed already in latest code base.  Would you please try
again using the latest nightly build?   Thanks!

Tinny
----- Original Message -----
From: "Gareth Reakes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 03, 2002 3:57 AM
Subject: Re: Wrapper4InputSource does not work since get/set Encoding are
not virtual on InputSource!


> Hi,
> could you open a Bugzilla entry so we can keep track of this?
>
> thanks
>
> Gareth
>
>
> On Mon, 2 Dec 2002, Urs Muff wrote:
>
> > /*
> >  * $Id: Wrapper4InputSource.hpp,v 1.5 2002/11/04 15:00:21 tng Exp $
> >  */
> >
> > Implementing those functions in Wrapper4InputSource does not really
help,
> > since InputSource does not declare them virtual therefore they will be
not
> > overwritten.  This leads to the fact that the DOMInputSource
> > (Wrapper4DOMInputSource) is virtually unusable in combination with
> > DOMBuilder, since the parse method is using Wrapper4InputSource
internally,
> > but the encoding is always empty (default of InputSource).
> >
> >     const XMLCh* getEncoding() const;
> >     const XMLCh* getPublicId() const;
> >     const XMLCh* getSystemId() const;
> >     void setEncoding(const XMLCh* const encodingStr);
> >     void setPublicId(const XMLCh* const publicId);
> >     void setSystemId(const XMLCh* const systemId);
> >
> > Easy fix: declare those function virtual in SAX/InputSource.hpp.
> >
> > - Urs C. Muff
> > Systems Architect   - Research Lab
> > [EMAIL PROTECTED]  - X6360
> > +1 (303) 894 3360
> >
> >
>
> --
> Gareth Reakes, Head of Product Development  +44-1865-203192
> DecisionSoft Limited                        http://www.decisionsoft.com
> XML Development and Services
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to