Hi Boris,

Yeah, you are correct.  Would you please fill a jira?
I will fix it asap.

Best Regards

Freeman

On Sat, Mar 8, 2008 at 12:13 AM, boris <[EMAIL PROTECTED]> wrote:

>
> Hi Freeman,
>
> actually the patch that you've made is in the
> "CxfBcProviderMessageObserver", but in "CxfBcProvider" there is no such
> thing like:
>
>        if (exchange.getStatus() != ExchangeStatus.ACTIVE) {
>            return;
>        }
>
> so the done(exchange) comes also in the process(exchange) method of a
> CxfBcProvider and causes that the ws-call is made twice.
>
> best regards,
>
> boris
>
>
> Freeman Fang wrote:
> >
> > Hi Boris,
> >
> > What's the servicemix version you are using, I think this bug get
> resolved
> > already after smx 3.2.1 release.
> >
> > https://issues.apache.org/activemq/browse/SM-1159
> >
> > track this issue
> >
> > Freeman
> >
> > On Fri, Mar 7, 2008 at 8:43 PM, boris <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> Hi,
> >>
> >> I'm using the cxf-bc as a provider in my scenario. When I send an InOut
> >> to
> >> a
> >> cxf-bc, the CxfProvider processes both sendSync(exchange) and
> >> done(exchange), and makes the ws-call twice!
> >>
> >> Boris
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/cxf-bc-provider-processes-done%28exchange%29-tp15891215s12049p15891215.html
> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/cxf-bc-provider-processes-done%28exchange%29-tp15891215s12049p15898684.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>

Reply via email to