gnodet wrote:
>
> Let me explain my thoughts about CXF / JBI.
> For those who don't know, JBI has two concepts which are Binding
> Components
> and Service Engine. The Binding Component is in charge of the protocol
> normalization,
> while the Service Engine is in charge of providing a business service. In
> CXF, both
> are linked somehow, but for a good JBI integration, they need to be split.
>
> The two modules (JBI binding and JBI transport) will be used in a Service
> Engine.
> The transport was taken from the JBI integration in CXF and updated a bit,
> while
> the binding is new. The binding is in charge of transforming the JBI
> normalized message
> (using a wrapper defined in the JBI spec for WSDL 1.1 messages) to / from
> CXF messages.
>
> Another component will be a Binding Component which will transform an
> incoming soap
> message to a JBI normalized message, while handling all the WS-*
> specifications.
> It will also handle the client side.
>
>
Hi,
I have two little & cute (maybe not) questions:
1°/ Performance
If I have two services that want to communicate between each other, I have
two solutions, one is without ESB, I developed CXF webservices, one is
calling the other so let's say we have one client and the 2 webservices:
Client
--(SOAP/HTTP)--> [CXF HTTP transport + binding transforpation ] WS1 [CXF
HTTP transport + binding transforpation ]
--(SOAP/HTTP)--> [CXF HTTP transport + binding transforpation ] WS2 [CXF
HTTP transport + binding transforpation ]
--(SOAP/HTTP)--> Client
The other solution (ESB powered):
Client
--(SOAP/HTTP) --> [CXF transport ] CXF-BC [CXF transport + binding
transforpation ]
--(JBI normalized message)-->[CXF JBI transport + binding transforpation ]
WS2 [CXF JBI transport + binding transforpation ]
--(JBI normalized message) --> CXF-BC [ JBI to SOAP/HTTP transformation]
--(SOAP/HTTP)--> CLIENT
Here we have only two services inside the jbi environment so the overhead of
BC may probably remove all the benefits. But how is the performance if the
numbers of services increase (4or5, the machines must survive).
2°/ Updating the CXF component
I have one problem, I need to upgrade the jaxws-api.jar library that is used
inside servicemix to use some webservices that have been previously
developed.
Is it possible to use the last release of CXF? I downloaded the archive and
I will try to replace it in two spots:
- in the maven repository: because when i compile using maven install on the
pom.xml of my SE-su, I see it's calling the servicemix-se dependency... I
went to subdependency again and again up to javax.xml.ws, and I could change
the jaxws-api...
- in the CXF-SE component installer i will change the library, so the CXF
will understand the new classes at runtime.
Plz stop me, if I am wrong.
By the way, how the servicemix-cxf-se evolved? Does it need to be modified
when a new version of cxf is released ?
TY
Brice
--
View this message in context:
http://www.nabble.com/ServiceMix---CXF-integration-tp10177803p17255177.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
