• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problem in running apache CXF webservice in weblogic 10 server

 
arish sarkar
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I'm new to apache CXF web service. Currently I'm using CXF 2.2.9 to build a web service and trying to deploy deploy in weblogic 10.0.1.0 version. I'm deploying the service in a WAR file. But, at the time of invoking the service I'm always getting the following exception. Please advice the solution.

[java] Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Unable to access unsupported property javax.xml.stream.supportDTD
[java] at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
[java] at $Proxy44.processOrder(Unknown Source)
[java] at demo.order.client.Client.main(Client.java:26)
[java] Caused by: org.apache.cxf.binding.soap.SoapFault: Unable to access unsupported property javax.xml.stream.supportDTD
[java] at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:75)
[java] at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:46)
[java] at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
[java] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
[java] at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:99)
[java] at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
[java] at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
[java] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
[java] at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:700)
[java] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2261)
[java] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2134)
[java] at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1988)
[java] at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
[java] at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:639)
[java] at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
[java] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
[java] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:487)
[java] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
[java] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
[java] at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
[java] at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
[java] ... 2 more
[java] Java Result: 1

Note:
1. I have the weblogic-application.xml in META-INF and it has the following entry,

<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90">
<application-param>
<param-name>webapp.encoding.default</param-name>
<param-value>UTF-8</param-value>
</application-param>
<prefer-application-packages>
<package-name>javax.jws.*</package-name>
</prefer-application-packages>
</weblogic-application>
 
Darrel Davis
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't have any info specifically about your case since I'm just starting to look at CXF myself and will be deploying to Weblogic 10.3.x also. One thing I thought of was that we had to tell weblogic to prefer libraries we included with our webapp instead of the installed ones, which caused us tons of headaches due to WL's older libs and conflicts. We had to put the following block of xml in the weblogic.xml file, telling WL to use our libs over theirs:

<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>

It might help.

-darrel
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic