>> and what about the sun.misc.BASE64Decoder ???? > > And what if you're not on that JDK? The problem with using any other > decoder, including Xerces', is that not everybody uses those components. > Until Sun standardizes a BASE64 API in the JDK, there's no good answer. > > -- Scott > >
What about to include(copy) the base64 code handling from xerces to xml-sec? This is not a thing that i like doing, but it�s true that there is not dependece between xerces and xml-sec(I don't know if there is anyone that has tested it with outher dom parsers). I think that the license is the same, and we can copy and modified, to mimic the old beahviour. Anyway my patch don't remove the old code, it only forwards the decode(string) and encode(byte) to the same function in xerces. The old ones with the integer are still working. The speed-up and memory consumptions reductions are really mesourable. Regards, Raul Raul
