Re: Issue with WSDL or CXF
Okay so I setup the CXF logging interceptor and this is what I now see...
Feb 14, 2008 9:48:24 AM org.apache.cxf.interceptor.LoggingInInterceptor
logging
INFO: Inbound Message
Encoding: UTF-8
Headers: {cache-control=[no-cache], content-type=[text/xml; charset=UTF-8],
connection=[keep-alive], host=[localhost:8080], soapaction=[""],
transfer-encoding=[chunked], accept=[*], user-agent=[Java/1.6.0_04],
pragma=[no-cache]}
Messages:
Message:
Payload: http://schemas.xmlsoap.org/soap/envelope/";>
--
Feb 14, 2008 9:48:25 AM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.frontend.SimpleMethodDispatcher.getMethod(SimpleMethodDispatcher.java:96)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56)
at
org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:77)
at
org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:264)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:170)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCXFServlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Feb 14, 2008 9:48:25 AM
org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
INFO: Outbound Message
---
Encoding: UTF-8
Headers: {}
Messages:
Payload: http://schemas.xmlsoap.org/soap/envelope/";>soap:ServerFault
occurred while
processing.
--
It seems that the soap:body is empty!!! Why is this happening??? Knowing me
I am making a stupid mistake on my WSDL somewhere. Although, I used one of
the simple examples as my template and just changed some of the XSD and WSDL
tags to fit my situation. Notice anything out of the ordinary? Or maybe I am
not setting up a configuration parameter somewhere. Again, I am just running
the test client class that CXF generates for me...
-Kyle
Next step Wireshark setup...
--
View this message in context:
http://www.nabble.com/Issue-with-WSDL-or-CXF-tp15469111p15480901.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Issue with WSDL or CXF
Daniel, I noticed I am receiving this exceprtion on the server side. I am running Tomcat 6.0.14. Feb 14, 2008 9:35:32 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now java.lang.NullPointerException at org.apache.cxf.frontend.SimpleMethodDispatcher.getMethod(SimpleMethodDispatcher.java:96) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:57) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:77) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:264) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:170) at org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCXFServlet.java:148) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) I am now in the process of setting up logging with CXF and Wireshark. Not sure if the above exception explains anything that may stand out an be obvious. -Kyle -- View this message in context: http://www.nabble.com/Issue-with-WSDL-or-CXF-tp15469111p15480789.html Sent from the cxf-user mailing list archive at Nabble.com.
Issue with WSDL or CXF
I have a Simple WSDL from which I generate the client and server code using
the applicable Maven2 plugins. My WSDL is as follows:
http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:user-service="http://ws.user.service.websend.agfa.com";
xmlns:user-model="http://model.ws.user.service.websend.agfa.com";
targetNamespace="http://ws.user.service.websend.agfa.com";>
http://model.ws.user.service.websend.agfa.com";
xmlns:user-model="http://model.ws.user.service.websend.agfa.com";>
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:8080/UserService"/>
Whenever I run the generated Client code I receive the following error:
Feb 13, 2008 5:00:29 PM
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromWSDL
INFO: Creating Service {http://ws.user.service.websend.agfa.com}UserService
from WSDL:
http://localhost:8080/com.agfa.websend.server.ws.user/services/UserService?wsdl
Invoking logon...
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: Fault
occurred while processing.
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:175)
at $Proxy25.logon(Unknown Source)
at
com.agfa.websend.service.user.ws.UserServicePortType_UserService_Client.main(UserServicePortType_UserService_Client.java:44)
Caused by: org.apache.cxf.binding.soap.SoapFault: Fault occurred while
processing.
at
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:70)
at
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208)
at
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:96)
at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:183)
at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:56)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:429)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1955)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1791)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:575)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:208)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:276)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:222)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
... 2 more
Is this a bug with CXF or is my WSDL bad??? I also run the validate option
for the wsdl2java command I have included my Maven2 POM as well:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.agfa.websend.server.ws
user
1.0.0
war
apache-snapshots
Apache SNAPSHOT Repository
http://people.apache.org/repo/m2-snapshot-repository/
true
apache-incubating
Apache Incubating Repository
http://people.apache.org/repo/m2-incubating-repository/
java.net
http://download.java.net/maven/1/
legacy
apache-plugin-snapshots
Apache Maven Plugin Snapshots
http://people.apache.org/repo/m2-snapshot-repository
Using CXF with an Eclipse RCP Application
I created a CXF OSGi bundle using the Eclipse Plug-in form Existing JAR archive wizard. I used the latest SNAPSHOT CXF JAR: cxf-2.1-incubator-SNAPSHOT.jar I then added the org.apache.cxf package to the import-packages of my manifest.mf When I try to call my web services from my RCP application I receive the following error: !ENTRY org.eclipse.osgi 4 0 2008-02-08 16:53:50.999 !MESSAGE Application error !STACK 1 javax.xml.ws.WebServiceException: Provider com.sun.xml.ws.spi.ProviderImpl not found at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:38) at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:133) at javax.xml.ws.spi.Provider.provider(Provider.java:83) at javax.xml.ws.Service.(Service.java:56) at javax.xml.ws.Service.create(Service.java:691) at cxf_client_test.Application.cxf(Application.java:22) at cxf_client_test.Application.start(Application.java:34) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) Caused by: java.lang.ClassNotFoundException: com.sun.xml.ws.spi.ProviderImpl at java.lang.ClassLoader.findClass(ClassLoader.java:358) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.eclipse.core.runtime.internal.adaptor.ContextFinder.loadClass(ContextFinder.java:124) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:34) ... 19 more My understanding is that it should be calling the ProviderImpl provided by CXF. Has anyone had any luck calling Web Services via an Eclikpse RCP application??? If so any advice or help here would be much appreciated!!! -- View this message in context: http://www.nabble.com/Using-CXF-with-an-Eclipse-RCP-Application-tp15364789p15364789.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: OSGi bundling
To whom it may concern, I would also like to try out CXF OSGi bundles. I would love to use CXF in my Eclipse RCP application I am writing. You mention there is a small (untested) maven project to create the bundles. I would like to try it out in my environment if possible. Where can I locate it to give it a whirl. Regards, Kyle gnodet wrote: > > We're currently working on using CXF inside ServiceMix, so I've just > committed a small maven project to create a bundle for CXF, though this is > not tested yet and may not include everything you will need right now. > However, any feedback would be welcome. > > On Nov 19, 2007 5:27 PM, Roshan A. Punnoose < > [EMAIL PROTECTED]> wrote: > >> Is there incubation code set up for the cxf OSGi bundling that is >> targeted for Dec.15? I want to try it out now. :) >> >> Roshan >> > > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/axis-vs-cxf%2C-which-is-better--tp13755334p15363956.html Sent from the cxf-user mailing list archive at Nabble.com.
