OK, problem solved. It is a bug in the current dom4j-release (1.4). It does not occur in older versions. But it is already fixed in an actual CVS-snapshot of dom4j.
Tanks for any help. Peer.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
