Hmm, seems like this problem is in dom4j and was fixed by a patch applied 5
weeks ago.  Is it possible for Jelly to use a more recent version of dom4j?

Cheers,

--
knut

Reply via email to