Java的更新1.6.0_26导致SOAP异常 - NoClassDefFoundError的:无法初始化FastInfosetReflection [英] Java Update 1.6.0_26 Causes SOAP Exception - NoClassDefFoundError:Could not initialize FastInfosetReflection

查看:1104
本文介绍了Java的更新1.6.0_26导致SOAP异常 - NoClassDefFoundError的:无法初始化FastInfosetReflection的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个小应用程序,使一个SOAP请求到Web服务。它没有证书或专项安全方面的考虑,只是一个基本的小程序和互联网服务。在几台计算机更新Java来1.6.0_26后,我可以说没有,该更新会导致以下异常疑问。 ($ P $的Java版本pvious仍然工作)

I have an applet that makes a SOAP request to a web service. It has no certificates or special security considerations, just a basic applet and webservice. After updating Java on a few computers to 1.6.0_26 I can say without a doubt that the update causes the following exception. (Previous versions of Java still work)

com.sun.xml.internal.messaging.saaj.soap.MessageImpl saveChanges
SEVERE: SAAJ0540: Error during saving a multipart message
com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Error during saving a multipart message
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)

...

java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.internal.messaging.saaj.util.FastInfosetReflection
   at com.sun.xml.internal.messaging.saaj.util.transform.EfficientStreamingTransformer.transform(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl.getContentAsStream(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.getHeaderBytes(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.saveChanges(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(Unknown Source)
   at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)

有谁知道是什么原因造成这样或有任何变通办法?

Does anyone know what is causing this or have any workarounds?

如果有必要,我有一个较长的异常堆栈跟踪,我可以张贴。

If necessary, I have a longer exception stack trace that I can post.

感谢。

推荐答案

这是从 http://java.net /节点/ 701033

我要学习,我需要签署所有.jar文件,该applet使用,它们都必须使用相同的证书签名(也就是即使我用的库文件已经签署 - 但由其他签约权威 - 我需要用我用它来签名Applet的主罐)相同的证书重​​新签字。在此之后,小应用程序,现在开始了罚款并不会尝试访问任何非法系统属性,也不尝试找到任何丢失的类,从而避免这些异常。

I had to learn that I need to sign ALL .jar files that the applet uses AND they all have to be signed with the same certificate (i.e. even though the library files I were using WERE already signed - but by an other signing authority - I needed to re-sign them with the same certificate that I use to sign the applet's main-jar). After that the applet now starts up fine and does not try to access any illegal system property nor does it try to locate any missing class thereby avoiding these exceptions.

我不是100%正面无论这是一个preREQ与否:在试图让这个跑我也迁移到最新的Java 6 JRE(即对Sun JRE这是1.6.0_17,对于过程IBM JRE这将是1.6.0sr7)。

I am not 100% positive whether that's a prereq or not: in the process of trying to get this running I also migrated to the very latest Java 6 JRE (i.e. for Sun JRE that's 1.6.0_17, for an IBM JRE that would be 1.6.0sr7).

通过这些步骤都小程序我现在工作正常使用SOAP与服务器进行通信,并与双方提到的JRE这样做。

With these both steps my applet is now working fine using SOAP to communicate with the server and it does so with both mentioned JREs.

HTH,

这篇关于Java的更新1.6.0_26导致SOAP异常 - NoClassDefFoundError的:无法初始化FastInfosetReflection的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆