Agreed.  I think it warrants a fix in v1.2.7.  I'll let you know the status
tonight.

-Mark

> -----Original Message-----
> From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 07, 2002 10:35 AM
> To: Log4J Developers List
> Subject: RE: DomConfigurator Entity Resolver update
> 
> 
> 
> After unit testing, I propose that this addition is 
> incorporated into the 
> 1.2 branch.
> 
> At 09:47 07.10.2002 -0700, you wrote:
> >OK.  I'm going to get this integrated tonight. Might take a 
> bit longer to
> >work up various tests ,etc.
> >thanks,
> >-Mark
> >
> > > -----Original Message-----
> > > From: Paul Austin [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, October 07, 2002 8:45 AM
> > > To: Log4J Developers List
> > > Subject: RE: DomConfigurator Entity Resolver update
> > >
> > >
> > > Mark,
> > >
> > > The orginal code returned the log4j dtd if the filename in
> > > the dtd started
> > > with file: and ended with log4j.dtd. This worked with
> > > xerces2.1 but failed
> > > to work with xerces2.2 as the url with 2.2 was just
> > > log4j.dtd. So I changed
> > > the check to look just for a url ending in log4j.dtd.
> > >
> > > Paul
> > >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > > Sent: October 3, 2002 11:21 PM
> > > To: Log4J Developers List
> > > Subject: RE: DomConfigurator Entity Resolver update
> > >
> > >
> > > Paul,
> > >
> > > Thanks the the patched patch :-).  Can you describe what 
> problem the
> > > original version caused?
> > >
> > > I'm still going to look at applying the patch...soon...
> > >
> > > thanks,
> > > -Mark
> > >
> > > > -----Original Message-----
> > > > From: Paul Austin [mailto:[EMAIL PROTECTED]]
> > > > Sent: Wednesday, October 02, 2002 4:32 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: DomConfigurator Entity Resolver update
> > > >
> > > >
> > > > Guys,
> > > >
> > > > I found a bug in the bug fix which stopped it working, the
> > > file attached
> > > > fixes this problem.
> > > >
> > > > Paul Austin
> > > > Galdos Systems Inc.(tm)
> > > > [EMAIL PROTECTED]
> > > > Tel: +1 (604) 484-2761
> > > > Fax: +1 (604) 484-2755
> > > > http://www.galdosinc.com/
> > > >
> > > > Privileged or confidential information may be contained in this
> > > > message. If
> > > > this message was not intended for you, destroy it and notify us
> > > > immediately.
> > > > Opinions, conclusions, recommendations, and other
> > > information presented in
> > > > this message are not given or necessarily endorsed by my
> > > employer or firm.
> > > >
> > > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > > <mailto:[EMAIL PROTECTED]>
> > >
> >
> >--
> >To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> >For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 
> --
> Ceki
> 
> TCP implementations will follow a general principle of robustness: be
> conservative in what you do, be liberal in what you accept from
> others. -- Jon Postel, RFC 793
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 

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

Reply via email to