You’ll likely need to create an example/test case…. It looks like that should probably be calling super.getBindingOperationInfo(…) instead. Not 100% sure though.
Dan > On Apr 4, 2018, at 4:23 PM, Fabian Gonzalez <fabian.gonza...@mulesoft.com> > wrote: > > Hello, all > > I've opened a ticket because I think there may be a problem in the > operation info resolution in StaxDataBindingInterceptor when there are more > than one operation partaining to the same binding. > > https://issues.apache.org/jira/browse/CXF-7699 > > This results in an incorrect resolution of the exchange pattern for > bindings with more than one operation. > I would like to know if I am missing something or this is effectively an > issue. > > Thanks in advance, > > Fabian > > > -- > <http://www.mulesoft.com/> > Fabian Gonzalez, Software Engineer > > Juana Manso 999 6th floor, Buenos Aires, C1107CBS, Argentina > > O +54-11-5873-8258 <+54%2011%205353-4497> > > <https://www.linkedin.com/company/mulesoft> <https://twitter.com/mulesoft> > <https://www.facebook.com/MuleSoft> <https://videos.mulesoft.com/> We're > hiring! <http://www.mulesoft.com/careers> > > *NOTICE: This e-mail may contain confidential information. Any pricing > information contained in this communication is confidential MuleSoft > information. If you are not the addressee or the intended recipient please > do not read this e-mail and please immediately delete this e-mail message > and any attachments from your network mail system. If you are the addressee > or the intended recipient and you save or print a copy of this e-mail, > please place it in an appropriate file, depending on whether confidential > information is contained in the message, and please treat all MuleSoft > confidential information with heightened protection.* -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
