FW: [jdom-interest] & in namespace

[Andrew S. Townley]

Hi Jason,

I guess this means I should finally get off *my* duff and submit a patch
for the problem I had with the XMLOutputter and overriding its behavior
(some things are not protected that I think arguably should be, meaning
it isn't really designed for inheritance).  I'm a bit swamped for the
next couple of weeks.  Any idea how soon you're talking about doing the
next release?  I'd like to get this in and un-hack my hack, so to
speak...

Cheers,

ast

On Wed, 2006-05-03 at 17:43, Jason Hunter wrote:
> Bradley S. Huffman wrote:
> > "Deshpande, Aniruddha" writes:
> > 
> >> What do you feel? Is this a bug in JDOM? How should we proceed?
> > 
> > You look at the code to see what's going on, and if needed make a patch
> > like this. Brad
> > 
> > *** XMLOutputter.java	Fri Dec 10 19:31:50 2004
> > --- XMLOutputter.new	Wed May  3 09:03:19 2006
> > ***************
> > *** 1118,1124 ****
> >               out.write(prefix);
> >           }
> >           out.write("=\"");
> > !         out.write(uri);
> >           out.write("\"");
> >           namespaces.push(ns);
> >       }
> > --- 1118,1124 ----
> >               out.write(prefix);
> >           }
> >           out.write("=\"");
> > !         out.write(escapeAttributeEntities(uri));
> >           out.write("\"");
> >           namespaces.push(ns);
> >       }
> 
> Bingo.  Anyone see a reason this wouldn't be spec conformant?
> 
> BTW, JDOM's not dead.  I'm still engaged, just need to get off my duff 
> and do a 1.0.1 with the few small bugs we fixed since 1.0.  There hasn't 
> been much interest expressed in a 1.1 release.  JDOM already does 
> everything *I* care about.  Are there things people want in a 1.1 or 
> 2.0, or should we stay in happy maintenance mode.
> 
> -jh-
> _______________________________________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com
-- 
Join me in Dubrovnik, Croatia on May 8-10th when I will be speaking at
InfoSeCon 2006.  For more information, see www.infosecon.org.
***************************************************************************************************
The information in this email is confidential and may be legally privileged Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
***************************************************************************************************