Question

我一直在尝试做一个物体序列化和 Base64 编码结果。它与Sun Sulb合作:

Bean01 bean01 = new Bean01();
bean01.setDefaultValues();
ByteArrayOutputStream baos = new ByteArrayOutputStream();
new ObjectOutputStream( baos ).writeObject( bean01 );
System.out.println(Base64.encode(baos.toByteArray()));

不过,我想用Ong.apache.commons.codec.binary. base64 来做同样的事情,但这并不返回相同的字符串:

System.out.println (org.apache.commons.codec.binary.Base64.encodeBase64 (baos.toByteAray ()); (org.apache.commons.codec.binary.Base64.encodeBase64 (baos.toByteAray ());

用阿帕奇编码器对字节阵列进行正确的 Base64 编码的正确方式是什么?

Answer 1

实际上,您正在使用的 < commons- codec 版本和具体的 Sun 内部版本的 < strong > do 给与同样的结果。我想你认为他们给出不同的版本, 是因为你暗中将 < code> to String () 调用在一个阵列上, 当你这样做时:

System.out.println(org.apache.commons.codec.binary.Base64.encodeBase64(baos.toByteArray()));

其中肯定不打印数组内容。相反,这将只打印数组引用的地址。

我写了以下程序来测试编码器相互对立。您可以从下面的输出中看到结果相同:

import java.util.Random;

public class Base64Stuff
{
    public static void main(String[] args) {
        Random random = new Random();
        byte[] randomBytes = new byte[32];
        random.nextBytes(randomBytes);

        String internalVersion = com.sun.org.apache.xerces.internal.impl.dv.util.Base64.encode(randomBytes);
        byte[] apacheBytes =  org.apache.commons.codec.binary.Base64.encodeBase64(randomBytes);
        String fromApacheBytes = new String(apacheBytes);

        System.out.println("Internal length = " + internalVersion.length());
        System.out.println("Apache bytes len= " + fromApacheBytes.length());
        System.out.println("Internal version = |" + internalVersion + "|");
        System.out.println("Apache bytes     = |" + fromApacheBytes + "|");
        System.out.println("internal equal apache bytes?: " + internalVersion.equals(fromApacheBytes));
    }
}

这里显示它运行的输出 :

Internal length = 44
Apache bytes len= 44
Internal version = |Kf0JBpbxCfXutxjveYs8CXMsFpQYgkllcHHzJJsz9+g=|
Apache bytes     = |Kf0JBpbxCfXutxjveYs8CXMsFpQYgkllcHHzJJsz9+g=|
internal equal apache bytes?: true

Answer 2

http://commons.apache.org/codec/"rel="no follow">commons-codec主页:

Codec was formed as an attempt to focus development effort on one definitive implementation of the Base64 encoder. At the time of Codec s proposal, there were approximately 34 different Java classes that dealt with Base64 encoding spread over the Foundation s CVS repository. Developers in the Jakarta Tomcat project had implemented an original version of the Base64 codec which had been copied by the Commons HttpClient and Apache XML project s XML-RPC subproject. After almost one year, the two forked versions of Base64 had significantly diverged from one another. XML-RPC had applied numerous fixes and patches which were not applied to the Commons HttpClient Base64. Different subprojects had differing implementations at various levels of compliance with the RFC 2045.

我认为你的问题是"不同层次"的遵守

我的建议: 选择一个基数64 编码器/编码器, 并坚持它

友情链接