> I don�t need to, because, i don�t use dom neither jdom, i developed myownprints> small JAXB, so I read the > XML into my generated Java structure, > when I need to sign some area y use, a method of the structure that> the canonized XML.
It doesn't matter you use for representing the XML. You still need to c14n it. One bit of difference in the input and you will break your signature. Without c14n it would be hard enough to be compatible with your own implementation.
I read the XML, I modify it all the times I want, when I print it or save to the XML database It�s always in c14n because the structure .toXML() canonizes it. so the signature always correspond to the saved XML.
Well.. is the XML you are outputting always the same or does the output conform to one or more C14N standards?
If it's the same you will be able to archieve interop with your own app, but not with others. If you are somehow able to output C14N output, you might be able to archieve limited interop with other providers.
That's not to say that it's not worthwhile to do your own, but it'susuallynot worth the trouble because of the effort involved, and it's usually impossible to change anything without breaking it. As soon as you have to add something you usually have to start from close to the beginnen :)
I don�t get it, after I have signed it, I am not going to modify it, and before signing it I can make all the changes I need.
I am sorry.. wasn't being clear. I meant that if your requirements change in such a way that you need to change the code. It is usually quite a challenge to change code like that because it's usually quite rigid.
I'd be (pleasantly) surprised ;-)
jeje, maybe.
Erwin
