Hi Theo
> How can I tell the XMLWrite that he escapes Special Characters in the
> Output like that:
> & => &
During some optimisation and tuning experiments, I'd accidentally turned off
the escaping of special characters in XMLWriter. (Whoops, sorry about that
;-).
I've just checked in a patch which fixes this. I've manually kicked off a
daily build too so if you download a daily snapshot (or take the latest from
CVS) you will get the patch.
If you wanted to do some other kind of escaping you could always derive from
XMLWriter and overload the following methods that do the actual encoding:-
protected String escapeElementEntities(String text);
protected String escapeAttributeEntities(String text);
> Is the org.dom4j.Document serializable for storing in a Database?
I'd always recommend storing the text (XML) of a Document rather than
serialized Java objects. Serialization is an opaque and often very fragile
format for storing Java objects - its main use is for short lived
serializations such as RMI calls.
As it happens someone is actively developing a serialization implementation
right now which should be available soon. But I would only recommend it for
use in (say) RMI.
When persistence is involved, I'd always store it as plain XML text by
default. Then any tool can be used to extract and process the XML data.
An alternative approach is to store a persistent object model, e.g. having
tables Document, Element and Attribute. So you could have your own DbWriter
which would write a Document (or fragment) to a database.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-dev
