Hi,
I use camel for more that one year now and it is actual great for
integration questions. One thing that I always mess around with is
calling external web services (soap in general). And IMHO this is a
central use case for soa / integration purposes. I received the
impression that this central use case has not the weight it should have
in an integegration framework like camel. E.g. most examples with camel
and cxf shows how to expose a web service, not how to consume one; there
are maven archtypes which create new projects again only for exposing a
service - there is no archtype for consuming one. Even the camel in
action book mostly covers cxf to use as a provider. So I think this
should be made much easier with much more examples. (or that easy that
no example is neccessary) If you know openesb / glassfish esb there it
is a matter of drag and drop a wsdl to the project, use an operation as
endpoint (which you can use from a drop down box) and specify the
message-mapping (all is supported by easy clicky clicky)
Don't get me wrong. I really like camel very much, but I always have
some problems with:
* what component should I use (http, cxf, spring-ws) I think cxf should
be the standard but should be easier to use
* most of my camel routes run in smx. my acutal problem in smx 4.5
(which seems to be an osgi-problem) is that I get an exception which
says that no org.apache.cxf.jaxws.spi.ProviderImpl could be found. And I
already tried 4 hours to fix this issue without success..
These hurdles makes it to a costly task to implement a route which
should call a service. IMHO this should not take longer that 5 mins to
implement that if you already have a wsdl for the service.
I hope my suggestions are understandable / useful.
I which you all Happy Easter,
regards,
Marco Westermann
