Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 128CF11173 for ; Thu, 15 May 2014 05:46:55 +0000 (UTC) Received: (qmail 78200 invoked by uid 500); 14 May 2014 22:23:20 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 77996 invoked by uid 500); 14 May 2014 22:23:19 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 77861 invoked by uid 99); 14 May 2014 22:23:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 May 2014 22:23:16 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.249.186.197] (HELO sosnoski.com) (72.249.186.197) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 May 2014 22:22:59 +0000 Received: from linux-a5lu.site (ip-58-28-158-218.static-xdsl.xnet.co.nz [58.28.158.218]) by sosnoski.com (Postfix) with ESMTPSA id A073A50C83; Wed, 14 May 2014 22:22:34 +0000 (UTC) Message-ID: <5373ECA8.1010904@sosnoski.com> Date: Thu, 15 May 2014 10:22:32 +1200 From: Dennis Sosnoski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: dev@cxf.apache.org, Aki Yoshida , Daniel Kulp Subject: Re: CXF 3.0 builds tomorrow.... References: <537119D4.2010902@sosnoski.com> <884CE455-AD41-42D6-99A1-97E193A88E83@apache.org>

In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Aki and I stepped on each other with commits yesterday because of mailing list lags and lack of coordination, but no harm done - we did the same thing in different ways, so I can just revert my change after 3.0.0. Should be good to go. - Dennis On 05/15/2014 06:19 AM, Daniel Kulp wrote: > Thanks Aki and Dennis, > > Things are looking good. I�ve just reviewed the NOTICE/LICENSE stuff and that looks OK. Did a little more testing and things look fine for 3.0. I think anything left can push to 3.0.1. > > Thus, I plan on starting the builds shortly. Shout ASAP if there�s an issue. :-) > > Dan > > > > On May 14, 2014, at 4:59 AM, Aki Yoshida wrote: > >> For the problem that we thought there is, an empty partial response >> being returned as an soap envelope with http 202 was a ghost. >> On the network, the soap content is definitely not sent. I see each >> request is returned with the expected 202 response, as >> >> HTTP/1.1 202 Accepted >> Content-Type: text/xml;charset=UTF-8 >> Content-Length: 0 >> Server: Jetty(8.1.15.v20140411) >> >> The bogus content shows up only in the server side logging, as >> >> ID: 1 >> Response-Code: 202 >> Encoding: UTF-8 >> Content-Type: text/xml >> Headers: {} >> Payload: > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:d050fe7f-ed97-4d25-9fdf-84b4776fffa8> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous> xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://www.w3.org/2005/08/addressing/unspecified >> >> >> So this is apparently not a decoupled endpoint issue but just a >> logging issue. So we can fix it in 3.0.1. >> >> regards, aki >> >> -------------------------------------- >> >> >> 2014-05-13 23:44 GMT+02:00 Aki Yoshida : >>> Hi Dennis, Dan, >>> I think the oneway decoupled WS-RM scenario seems to be working fine >>> when I look at the client side log transcription. >>> http://pastebin.com/wRReBcqz >>> >>> One error, I believe, that I saw while I was trying out a few other >>> things was the CloseSequence generation. I wrote to the dev list about >>> this a few hours ago. >>> >>> Another error which Dennis mentioned to me and I can confirm is the >>> partial empty response is not correctly recognized as an partial empty >>> message at the server side. As a result, an empty soap envelope with >>> the default ws-a header is returned with http 202 over the http >>> response. I suppose this is resulted from some change somewhere in the >>> code that is not setting the correct state of the partial message. But >>> it seems this problem came in a while ago. I wanted to look at it >>> today but didn't get to it. But I think this won't take time. If I can >>> get a few hours tomorrow, I can look into it. But it won't harm much >>> even the content is included as long as the http status is set to 202 >>> to inform the client to ignore the content. In that case, we can >>> postpone this to 3.0.1. >>> >>> regards, aki >>> >>> >>> >>> 2014-05-13 17:07 GMT+02:00 Daniel Kulp : >>>> Dennis, >>>> >>>> Any updates? Just trying to figure out what�s left. :-) >>>> >>>> Dan >>>> >>>> >>>> >>>> On May 12, 2014, at 2:58 PM, Dennis Sosnoski wrote: >>>> >>>>> Hi Dan, >>>>> >>>>> RM is broken for oneway operations with a decoupled endpoint at present. I'm trying to track the problem down, and Aki has also taken a look. If I can't fix it myself I'll add a test case so you can take a look. >>>>> >>>>> I don't know that this would qualify as a show stopper, but it's pretty significant and should be an easy fix. >>>>> >>>>> - Dennis >>>>> >>>>> On 05/13/2014 02:38 AM, Daniel Kulp wrote: >>>>>> Now that we finally have email back (and thus can review/track commits, issues, call votes, etc�) I plan on doing the 3.0 builds real soon, hopefully tomorrow. It looks like everything major is now done. All snapshots are resolved, the tests seems to be passing, the RM issues are resolved, etc� Thus, I�d like to get this out. >>>>>> >>>>>> If you have anything that would be considered a show stopper, let me know ASAP. >>>>>> >>>>>> Thanks! >>>>>> >>>> -- >>>> Daniel Kulp >>>> dkulp@apache.org - http://dankulp.com/blog >>>> Talend Community Coder - http://coders.talend.com >>>>