weblogic 9.2.0's stax seems not working with xfire 1.2.4

SilverRing

浏览: 72640 次

最近访客更多访客>>

出离毛毛虫

scdhao

zhaojh10010

zhdongfu

博主相关

博客

微博

相册

留言

关于我

文章分类

社区版块

存档分类

博客分类：

Q and A

Weblogic Java Web Servlet 360

Problem Description:

Tomcat 5.5.17 is used as the web service host and weblogic 9.2.0 is used as the web service client.

If the return value of ws methods is a complex object, an exception will be thrown:

java 代码

Caused by: java.lang.UnsupportedOperationException
at weblogic.xml.stax.XMLStreamReaderBase.getTextCharacters(XMLStreamReaderBase.java:487)
at org.codehaus.xfire.util.stax.DepthXMLStreamReader.getTextCharacters(DepthXMLStreamReader.java:180)
at org.codehaus.xfire.util.stax.DepthXMLStreamReader.getTextCharacters(DepthXMLStreamReader.java:180)
at org.codehaus.xfire.aegis.type.basic.Base64Type.readObject(Base64Type.java:71)
at org.codehaus.xfire.aegis.type.basic.BeanType.readObject(BeanType.java:159)
at org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBindingProvider.java:162)
at org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding.java:206)
at org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedBinding.java:50)
at org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Client.onReceive(Client.java:382)

Thoughts:

According to the stacktrace, it seems weblogic's default xml stax parser doesn't work with xfire 1.2.4 if the method's return value is complex objects. Am thinking to replace the default parser with the one from xfire's library. But how?

Solution:

Set "prefer-web-inf-classes" to true.

xml 代码

<container-descriptor>
<prefer-web-inf-classes>trueprefer-web-inf-classes>
container-descriptor>

Based on the document:

If true, classes located in the WEB-INF directory of a web-app will be loaded in preference to classes loaded in the application or system classloader. Defaults to false. Value specified via console will be given precedence over this setting.

Problem solved!

分享到：

stax conflict between weblogic 9.2 and x ...

2007-03-21 16:06
浏览 3539
评论(1)
查看更多

1 楼 SilverRing 2007-03-22

Forgive me for being too careless and optimistic.

After weblogic's cache had been cleared, an exception occurred when the server was started.

weblogic.application.ModuleException: 
	at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
	at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
	at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
	at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
	at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
	Truncated. see log file for complete stacktrace
java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory
	at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
	at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper.java:244)
	at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelper.java:224)
	at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324)
	at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHelper.java:174)
	Truncated. see log file for complete stacktrace
>

发表评论

您还没有登录,请您登录后再发表评论

最近访客更多访客>>

博主相关

文章分类

社区版块

存档分类

最新评论