You do need a cxfbc:provider in this case.
The workflow is
external client ====>cxfbc:consumer====> cxfbc:provider====>external service(axis server in your case)
cxfbc:consumer will start a listening port and play the server side role, cxf bc:provider play the client side role.
Here cxfbc:consumer====> cxfbc:provider just like a bridge, we actually have a testcase which can demonstrate how this bridge works.
Btw, you need ensure your axis server not use rpc/encoded style as that style is quite old and not supported by cxf.
Ok ok, thanks for the answer! I understand..
I wrote that:
+ <cxfbc:provider wsdl="classpath:HelloService2.wsdl"+
With a consumer and a provider. But I still have a problem.
You said "cxfbc:consumer will start a listening port", indeed, when I'm going on http://localhost:8080 I fall on CFX (no more on Tomcat), as if it erase my previous listening port. So how can I change the listening port of my consumer ?
In cxfbc:consumer, you can specify locationURI using any port you want, this is the webservice url you exposed for external client.
And in cxfbc:provider, you can specify another locationURI which should be the same as the one used for your axis server, so that cxfbc:provider can talk to your server.