Hi,
Even communicate between two cxf se endpoints, I still suggest you
start from wsdl first, which make contract/interface very clear(also
you easily know what your message payload should be from the wsdl,
it's very useful you print out the log to debug or you need do some
transformation between endpoints, ) for the second se endpoint which
you can invoke from the first se endpoint, you can take a look at [1]
"Proxies" section which tells you how to invoke second se endpoint
from first se endpoint just like normal java method call.
Also I don't think your workflow all between different se endpoints,
generally it would need bc endpoints to talk to outside applications.
[1]http://servicemix.apache.org/servicemix-cxf-se.html
Freeman
On 2010-3-11, at 下午4:55, roshansn wrote:
Hi,
According to you there should be a bc with se always. Then how do you
communicate with two se's?
Thanks,
roshan
Freeman Fang wrote:
On 2010-3-11, at 下午4:14, roshansn wrote:
Hi,
wsdl auto generation is a feature of cxf-se componenet. But i need
to give a
my own wsdl as we give with cxf-bc.
The wsdl generated for cxf se endpoint is always built from the pojo,
you can't disable it.
I don't like to go to the code generation side. Because according to
the my
design it will be very difficult to manage my application.
Generally we recommend to use wsdl-first way because it can generate
code skeleton for you automatically,
it's more easy expecially when you use jaxb binding which need lots
of annotations, IMHO it's very hard and error prone part for you to
write it mannaully.
Secondly, use wsdl first way ensure that the contract/interface
between your cxf bc and cxf se endpoint (generally it's peer endpoint
for NMR) match each other, you need use same wsdl for your cxf bc
endpoint and for the cxf se wsdl2java tool.
I can't understand why use wsdl first bring difficulties to
management
of your application, frankly code first way is more popular user
scenario unless you already have some legacy code.
Freeman
thanks,
roshan
Freeman Fang wrote:
Hi,
I'm not sure I understand what you want, what you mean by "disable
wsdl auto generation feature"?
Even you use wsdl first approach(that's what we recommand), you
also
need provide a pojo class for the cxf se endpoint, but you can use
wsdl2java tool firstly to generate the code skeleton for you
automatically.
You may need take a look at the cxf-wsdl-first example to get
details
how to use wsdl2java maven plugin in pom.xml
Freeman
On 2010-3-11, at 下午3:38, roshansn wrote:
Hi,
Is there any way to disable wsdl auto generation feature from
cxf-se
component. I need to go with wsdl first approach.
Thanks,
roshan
--
View this message in context:
http://old.nabble.com/Contract-first-cxf-se-tp27860242p27860242.html
Sent from the ServiceMix - User mailing list archive at
Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
View this message in context:
http://old.nabble.com/Contract-first-cxf-se-tp27860242p27860513.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
--
View this message in context:
http://old.nabble.com/Contract-first-cxf-se-tp27860242p27860854.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
