Guys, currently (AFAIK) CXF Provider requires targetOperation to be specified on incoming message exchange in case when there are more than one operation on target service. See http://cwiki.apache.org/SM/discussion-forums.html#nabble-td19142533 for the problem. (case with one operation was fixed https://issues.apache.org/activemq/browse/SM-1225),
Don't you think that CXF Provider should determine the operation based on payload? If the WSLD uses document/literal style this is how it should work. How would you implement dynamic invocation (CXF Consumer -> CXF Provider) when you don't know in advance which operation client wants to invoke? Having endpoint (on consumer) per operation is not a nice solution because it in fact splits one service into many. On the other hand implementing mapping (root element -> operation) somewhere on ESB is redundant because it is already done in WSDL (and it's very ugly solution). Any thoughts? Was that already discussed somewhere and I missed that? -- View this message in context: http://www.nabble.com/CXF-Provider-dynamic-operations-invocation-tp20830984p20830984.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
