soap exception

I am getting a soap exception from MWS when calling a service that there are no return results for but when there is data it returns fine w/ no errors.

Am I missing something or do I need to put in some java code to catch this exception when there is no data or am I doing something incorrect on the IS side?

Any help appreciated. Thanks

What is the exception that you are getting returned?

Thanks,
Thomas

Seems like something might need to be caught on the MWS side because the IS implementation looks okay

electric.util.WrappedException: SOAPException( Client: [ISS.0088.9133] Error while encoding RPC output )
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getCompatibleException(WSClientDynamicProxy.java:411)
at com.webmethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:227)
at $Proxy4.getUpdatableConflictsList(Unknown Source)
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:585)
at com.webmethods.caf.faces.data.object.ObjectMethodContentProvider.refresh(ObjectMethodContentProvider.java:366)
at com.webmethods.caf.ccupdatableconflicts.CcUpdatableConflictsDefaultviewView.search(CcUpdatableConflictsDefaultviewView.java:197)
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:585)
at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
at com.webmethods.caf.faces.application.CAFMethodBinding.invoke(CAFMethodBinding.java:67)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
at javax.faces.component.UICommand.broadcast(UICommand.java:312)
at com.webmethods.caf.faces.component.ViewRoot.broadcastEvents(ViewRoot.java:202)
at com.webmethods.caf.faces.component.ViewRoot.processApplication(ViewRoot.java:116)
at com.webmethods.caf.faces.portlet.PortletLifecycle$InvokeApplicationPhase.execute(PortletLifecycle.java:660)
at com.webmethods.caf.faces.portlet.PortletLifecycle.phase(PortletLifecycle.java:247)
at com.webmethods.caf.faces.portlet.PortletLifecycle.execute(PortletLifecycle.java:142)
at com.webmethods.caf.faces.portlet.FacesPortlet.processAction(FacesPortlet.java:326)
at com.webmethods.portal.framework.portletcontainer.impl.PortletApplicationHandler.process(PortletApplicationHandler.java:477)
at com.webmethods.portal.framework.portletcontainer.servlet.PortletServlet.service(PortletServlet.java:58)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:286)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:171)
at com.webmethods.portal.framework.portletcontainer.PortletContainer.dispatch(PortletContainer.java:218)
at com.webmethods.portal.framework.portletcontainer.PortletContainer.process(PortletContainer.java:129)
at com.webmethods.portal.framework.portletcontainer.PortletContainer.processPortletAction(PortletContainer.java:107)
at com.webmethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.handle(RestfulPCAHandler.java:182)
at com.webmethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:438)
at com.webmethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371)
at com.webmethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
at com.webmethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at com.webmethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at com.webmethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:159)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

Most common cause for this error is mismatch between output signature of IS service and the actual data being returned by it. The data returned has exactly to match declared output signature. If there is a document expected, it has to be returned (even as null)

Alex is right. Try making the return variable as optional in IS service. This is what I do when I can expect an optional reponse from a web service. This may not be the best way, but it works.
P.S. You will need to regenerate WSDL and related artifacts after changes to the IS signature.

thanks adding a sequence step to catch when the data is null and return empty value fixed this