First I would define wsdlResource attribute for jsr181 endpoint. Next I would make sure that wsdl is correct - I think you are missing wsdl:binding node - which binds service with porttype.
Michal Taner wrote: > > Hi All, > > I am running in to problem when I try to expose a JSR181 component as a > web service. > The problem is that I am getting the following error when I send a request > to the web service. > > INFO: Fault occurred! org.codehaus.xfire.fault.XFireFault: Not enough > message parts were received for the operation. > at > org.codehaus.xfire.service.binding.ServiceInvocationHandler.fillInHolders(ServiceInvocationHandler.java:240) > at > org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:73) > at > org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131) > at > org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.java:64) > at > org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.java:38) > at > org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:113) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489) > at > org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441) > at > org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46) > at > org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595) > at > org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) > at > org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:595) > > The strange thing is that XFire only sees two parameters but there are > four in the request. When I change the signature of the method to one > parameter and send a request with one parameter it works. > > I have attached my sources with a unit test for the problem. > > Thanks in advance. > > With kindest regards, > > > Taner Gedikoglu > > > http://www.nabble.com/file/p12182626/logging.zip logging.zip > -- View this message in context: http://www.nabble.com/Problem-exposing-JSR181-component-as-a-Web-Service-tf4280047s12049.html#a12183214 Sent from the ServiceMix - User mailing list archive at Nabble.com.
