Hi,
I don't think you can really avoid going through NMR if you use SE-BC
architect with SMX3, which is defined in JBI specs.
But your NMR message payload may not use JBI wrapper, you can use soap
payload for your NMR message, this will save time to do the transform
between soap message and jbi message, you can add
useJBIWrapper="false" for your cxf bc endpoint.
Or if you use SMX4, you can access the cxf endpoint deployed into
smx4 container directly using http osgi service(this is very similar
as access a standalone cxf endpoint through http transport), which BC
not get involved at all in this case, you may need take a look at the
cxf-osgi example shipped with SMX4 kit.
Freeman
On 2010-1-11, at 下午1:37, roshansn wrote:
Hi guys,
I need to create a binding component to expose a web service. But I
am not
willing to use cxf binding component that is already given. Because
it will
help to reduce performance of the system. (always go through NMR)
Can anyone
give me an idea to solve it?
--
View this message in context:
http://old.nabble.com/Create-a-web-service-without-using-CXF-binding-componenet-tp27106112p27106112.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
