Looks like this is a bug in StringBuffer and not anything XML specific. So, in theory, lots of APIs could be fouled up as a result. I guess it is just more obvious with XML because so many strings are involved.

I too would be curious to know if this could be an issue using 1.4.1. and dom4j 3. Sounds like with 1.4.0 you'd be okay.

Hi Folks,

Does this bug

http://developer.java.sun.com/developer/bugParade/bugs/4724129.html

affect dom4j also?

I didn't prove it. I just found this bug report when seeking for another one.

Bye
Toby




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-dev

Reply via email to