Ok.. What difference between servicemix-service-engine and
servicemix-cxf-se?
Guillaume Nodet пишет:
On Wed, Apr 9, 2008 at 10:18 AM, ivan <[EMAIL PROTECTED]> wrote:
Ok, I use this example. I see following structure:
- wsdl-first-cxf-sa
- wsdl-first-cxfbc-su
- wsdl-first-cxfse-su
So, I need to develop wsdl-first-cxfse-su (change wsdl, implement
service-interface). Also wsdl-first-cxfbc-su contains the same wsdl. So, do
I need to provide my WSDL both wsdl-first-cxfbc-su wsdl-first-cxfse-su
projects?
If I understood right, project wsdl-first-cxfse-su is mix of functionality
of 2 archetypes: servicemix-cxf-se-service-unit and
servicemix-jsr181-wsdl-first-service-unit. First creates stub for SE,
another - creates STUB for generating sources from WSDL (wsdl2java).
Not exactly. The servicemix-cxf-se will host the service in a protocol
agnostic way (it does not even deal with SOAP). The servicemix-cxf-bc will
just create an HTTP/SOAP service and will send a JBI exchange to the cxf-se
for processing. The BC only deals with SOAP/HTTP, and the SE only deals
with your business logic.
Btw, servicemix-jsr181 is not used in the cxf-wsdl-first example.
Any comments are welcome :)
Thanks.
Freeman Fang пишет:
Hi Ivan,
We have a README with the example in the kit, no wiki so far
Freeman
ivan wrote:
Recenlty I have downloaded sources... Btw, is there some guide about
cxf-wsdl example? Like "Hello world BC"
Freeman Fang пишет:
Hi Ivan,
You can find src code from smx 3.2.1 release kit. [1] for kit
downloading.
[1]http://servicemix.apache.org/download.html
Regards
Freeman
ivan wrote:
So, cxf-wsdl-first... I could find wsdl-first-cxfse-su,
wsdl-first-cxfbc-su, wsdl-first-cxf-sa in servicemix sources... But instead
of this sources, is there some documentation? How should I mimic this
example from "0"?
Thanks :)
Guillaume Nodet пишет:
Just mimic what the cxf-wsdl-first example do and you'll have
your
solution. it will be much easier as you don't need to fully
understand the
JBI api to make this work. A web service is just an artifact
for a JBI
component, it does not need to *be* a JBI component, because JBI
components
are usually containers onto which artifacts are deployed
(artifacts being
service units).
2008/4/8 ivan <[EMAIL PROTECTED]>:
Ok.. Let start from another side. Our task is to create
web-service with
custom implementation, so no one existing component does not
implement
needed functionality. What is our architecture of application
and plan of
development?
