Hi Willem, Thank you for the quick fix. My complete trunk sync/build is taking time. So I just applied the same change to my local 2.5.0 source for a quick test. And now it is working fine.
When the trunk build is done, I can run the test with it. Thanks. Regards, aki On Wed, Dec 15, 2010 at 7:53 AM, Willem Jiang <[email protected]> wrote: > FYI，I just committed a patch of CAMEL-3426 into Camel trunk. > Please check out the latest Camel 2.6-SNAPSHOT for verification. > > On 12/14/10 10:03 PM, Willem Jiang wrote: >> >> Hi, >> >> I just reproduce the error by writing a simple test case as you >> described, and created a JIRA[1] for it. >> >> [1] https://issues.apache.org/jira/browse/CAMEL-3426 >> >> On 12/13/10 11:16 PM, Aki Yoshida wrote: >>> >>> Hi, >>> I have a simple scenario using the file endpoint that polls a file and >>> sends it to a oneway CXF endpoint that calls an external web service. >>> The scenario works fine with Camel 2.4.0 with CXF 2.2.11, but does not >>> work with Camel 2.5.0. >>> >>> The processing itself works fine with 2.5.0, but after the successful >>> completion of a call, the pipleline does not set the status of the >>> call, resulting in the file endpoint never commiting the operation and >>> the file remaining in the polling directory. >>> >>> As the same scenario that calls a request-response CXF service works >>> fine with Camel 2.5.0, the problem seems to be caused by some changes >>> in the Camel's pipeline behavior for oneway calls. >>> >>> I tried to debug the 2.4.0 and 2.5.0 pipeline code. However, the >>> change between these versions is significant and I could not identify >>> what was exactly causing the different behavior. I was wondering if >>> someone is aware of this problem and could point me to the solution. >>> >>> I would appreciate your comments. >>> >>> Thanks. >>> Regards, Aki >>> >> >> > > > -- > Willem > ---------------------------------- > FuseSource > Web: http://www.fusesource.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang >
