Hi,
You are still using servicemix-http with servicemix-jsr181?
As servicemix-jsr181 is kinda deprecated, I suggest you use servicemix-
cxf-se with servicemix-cxf-bc instead(As I said days ago, I don't
think cxf component can't work with your file component in the flow).
If you still get problem with cxf component, I'd like to see your
whole testcase.
Thanks
Freeman
On 2009-8-7, at 上午1:19, Brian Taylor wrote:
I finally got this to work by deleting the Load method from the Java
class so
that I would only have the one method Save. This now requires me to
only
provide one operation per class. Am I doing something terribly wrong
or is
everyone else having to do the same thing? If so, this really
worries me
about recommending ServiceMix and Fuse support to large grocery and
general
merchandising chains. Could you imagine the number of services
required when
each service can only have one operation?
Brian Taylor wrote:
Sorry to bump this again, but I notice on the servicemix page [1]
in the
'Consumer endpoint attributes' blue box that the defaultOperation
attribute is set on the JBI exchange if present otherwise it
defaults to
the QName of the root xml element. This appears that it assumes we
are
always using Wrapped parameters. What if we're using Bare?
[1] http://servicemix.apache.org/servicemix-http.html
http://servicemix.apache.org/servicemix-http.html
--
View this message in context:
http://www.nabble.com/HTTP-BC%3A-Mapping-SOAP-WS-Addressing-Actions-to-Target-Operations-tp24815914p24850870.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
