For the client side, you need a provider endpoint on CXF-BC. For the server side, you need a consumer endpoint on CXF-BC. Both endpoints are described at http://servicemix.apache.org/servicemix-cxf-bc.html This will take care of the SOAP/HTTP protocol.
Then you need to implement a client that will send a JBI exchange to the provider endpoint on the client side, and your service implementation on the server side. Both can be achieved using CXF-SE as described at http://servicemix.apache.org/servicemix-cxf-se.html For the client, you may want to use the CXF-SE proxy to avoid dealing with an xml request and use POJOs instead. Note that for everything to work, you will first need to write a WSDL to describe your service. On Thu, Sep 25, 2008 at 11:59 AM, manish_goyal <[EMAIL PROTECTED]> wrote: > > Hi, > I am trying one scenario in which i am using two different FUSE on different > machine. One of the FUSE having webservice deployed in it. another FUSE will > be calling that webservice. > I dont want to intrect directly with the FUSE which has webservice deployed > in it. > Client program can interact only via FUSE which call webservice . > > I need help to configure cxf-bc for that. > > Or if any alternate solution exists then please let me know. > > I am attaching document which contain detail information about this. please > refer this. > > please respond me as soon as possible. > http://www.nabble.com/file/p19666481/Http-Binding.doc Http-Binding.doc > Thanks. > -- > View this message in context: > http://www.nabble.com/help-need-cfx-http-binding-tp19642393p19666481.html > Sent from the cxf-user mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://open.iona.com
