and what about the sun.misc.BASE64Decoder ????
public static byte[] BASE64toByteArray(String pBASE64string) throws
Exception {
return new BASE64Decoder().decodeBuffer(pBASE64string);
}
public static String ByteArrayToBASE64(byte[] pByteArray) throws Exception
{
return new BASE64Encoder().encode(pByteArray);
}
----- Original Message -----
From: "Erwin van der Koogh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 25, 2004 3:55 AM
Subject: Re: AW: DO NOT REPLY [Bug 29188] New: - Minor clean-ups and speed/m
emory improvment
> > just a short note about Base64. I use the Base64 of XML
> > security in WSS4J functions and it works perfectly. Any
> > reason why to use the Xerces implementation?
>
> The Base64 encoding class in XML Security is quite a mess and I have been
> trying to replace it as well, with something standard, faster and
cleaner..
>
> > In addition the Base64 of XML security provides a way
> > to control line wrap, that is if I call
> > Sting xxx = Base64.encode(data, 0);
> > the line is not wrapped. Specifing a value > 0 (min. 8 I believe)
> > defines the maxiumum line length.
> >
> > One specific functions depends on the "no line wrap" mechanism
> > (interoperability reasons).
>
> .. but I don't think this is the time to do that. The right time to do
this
> is with the next version of the toolkit, when everything should be behind
a
> JSR105 layer and it will be obvious when people will be relying on our
> private code and when they are relying on the public interface.
>
> Any other thoughts?
>
> Erwin
>
