Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 57612 invoked from network); 18 Oct 2006 05:16:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Oct 2006 05:16:03 -0000 Received: (qmail 47291 invoked by uid 500); 18 Oct 2006 05:16:03 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 47264 invoked by uid 500); 18 Oct 2006 05:16:03 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 47255 invoked by uid 99); 18 Oct 2006 05:16:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2006 22:16:03 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [216.73.126.120] (HELO mail.envoisolutions.com) (216.73.126.120) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2006 22:16:01 -0700 Received: from [192.168.3.103] (c-71-205-191-164.hsd1.mi.comcast.net [71.205.191.164]) by mail.envoisolutions.com (Postfix) with ESMTP id B1FF71009D for ; Tue, 17 Oct 2006 22:08:12 -0700 (PDT) Message-ID: <4535B87B.2080908@envoisolutions.com> Date: Wed, 18 Oct 2006 01:15:39 -0400 From: Dan Diephouse User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: cxf-dev@incubator.apache.org Subject: Need Help with WS-A systest Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I just committed a bunch of code to enable client side fault handling. I got side tracked with correlation, but then decided the crap that I wrote was completely unncessary as we're already doing correlation in MAPAggregator... Somewhere along the way I seem to have broken WS-A as the systest no longer passes, but I can't for the life of me figure out what I did. There were two main changes. First, I set things up so that the transport is responsible for correlating the exchange (if possible - obviously its not always). This means the transport needs to set both the message.exchange and exchange.inMessage. Setting the exchange.inMessage actually does both, so I switched everything to use that. Second, I removed the partial response handling from ClientImpl. As I said in the commit message, it seems that the ws-rm implementation should provide its own MessageObserver. Or at the very least, we should provide some better way of figuring out if its a partial response. One option woudl be setting a PARTIAL_RESPONSE property in the message. Another would be creating a different message label - i.e. exchange.setMessage("partial", message) - and then we can test if the received message equals exchange.inMessage. Regardless, I tried adding the partial response checking back in and it still didn't work. Can someone more familiar with the WS-A code help shed some light? I'm thoroughly stumped. Most likely I'm doing something insanely stupid :-) - Dan -- Dan Diephouse (616) 971-2053 Envoi Solutions LLC http://netzooid.com