Many of the C14N spec can be done at the SAX level as the document is being
parsed and this will probably be the most performant way of reading a C14N
dom4j document.
e.g. all of the following could be done as an XMLFilter (I think) as its
mostly involved with text encoding (merging adjacent text
Hi James, Bob,
> >From a usability perspective, it might make sense to put all this
> functionality into a single 'Canonicaliser' that is capable of performing
> a
> C14N of any dom4j Document created in any way (either SAX, DOM or
> programatically).
>
> James
I let you both XML Masters decide
Hey!!
Could some of you guys please post a link to all this "Canonical XML" and
"Security Kit" you're talking about?
Thanks :-)
Jakob
___
dom4j-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-dev
> Could some of you guys please post a link to all this "Canonical XML" and
> "Security Kit" you're talking about?
IBM's security suite is here:-
http://www.alphaworks.ibm.com/aw.nsf/techmain/xmlsecuritysuite
Canonical XML spec is here:-
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
James
Hi colleages,
I currently get closer and deeper to soap w/A and therefore developed a set
of classes to map dom4j trees into a MIME Evelope (text/xml) using Java Mail
and Activation.
Sould I commit it in cvs into a own soap packages along with a TestUnit?
Have a nice time.
-Toby
--
GMX - Die
