Return-Path: Delivered-To: apmail-ws-woden-dev-archive@www.apache.org Received: (qmail 58206 invoked from network); 21 Nov 2007 17:14:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Nov 2007 17:14:13 -0000 Received: (qmail 17459 invoked by uid 500); 21 Nov 2007 17:14:01 -0000 Delivered-To: apmail-ws-woden-dev-archive@ws.apache.org Received: (qmail 17440 invoked by uid 500); 21 Nov 2007 17:14:01 -0000 Mailing-List: contact woden-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: woden-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list woden-dev@ws.apache.org Received: (qmail 17429 invoked by uid 99); 21 Nov 2007 17:14:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2007 09:14:01 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jpjhughes@gmail.com designates 64.233.162.235 as permitted sender) Received: from [64.233.162.235] (HELO nz-out-0506.google.com) (64.233.162.235) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2007 17:13:51 +0000 Received: by nz-out-0506.google.com with SMTP id l1so1975625nzf for ; Wed, 21 Nov 2007 09:13:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=qDVpGtBoI8FxHVGtxqBkhAPUE18WruVUtnDKVCdsWOU=; b=gNZMWPkVRNhZbVlW6hkJ9V/BBOPvG6qRNVx+KIpkK1NSdVoVKtkfF52C3gmpTUCVQBacIw97dXCf/pYRFNVc1tnRjQqo1FmguiRdoBi8LhM0OCIuhP8dDGa2RKYfubkxXzdkcwZFSI3h8Y6S16wx6Kl1GtJmp27gVv+v43PuH+0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=rmu+QTdhIZWXaxPbuebee/jod03/bGXZskPJ1HWb+rJp31kzbtva622FtL4NWgiiHv0geEcJxayoK4+gZRshwrvCOx/xdBzP1/F/sF+CqHFQjzK8NKmp9mHItWTy5DHZM/HGV6g+qQnE5DNjUmlYn+ZDi3qdrwYCeWmhw4/82uo= Received: by 10.141.99.4 with SMTP id b4mr3433443rvm.1195665198920; Wed, 21 Nov 2007 09:13:18 -0800 (PST) Received: by 10.140.186.21 with HTTP; Wed, 21 Nov 2007 09:13:18 -0800 (PST) Message-ID: Date: Wed, 21 Nov 2007 17:13:18 +0000 From: "Jeremy Hughes" Sender: jpjhughes@gmail.com To: woden-dev@ws.apache.org Subject: Re: Woden API Review wiki page In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 75e3ef1900cd25d3 X-Virus-Checked: Checked by ClamAV on apache.org One issue is the equals() method. As things stand there is an equals(WSDLComponent) method on WSDLComponent interface and implemented trivially on WSDLComponentImpl. Unfortunately if you compare two DescriptionElement objects the equals(Object) method is called which returns false. There is a fundamental problem with having a single implementation class implementing the WSDLComponent and WSDLElement interfaces. If I want to compare two DescriptionElement instances with each other then equals(Object) needs to be implemented (by DescriptionImpl) and that implementation needs to do the comparison at the XML infoset level. If I want to compare two Description instances (ie at the component model level) then equals(Object) needs to be implemented (by DescriptionImpl) and that implementation needs to do the comparison at the Component model level. There's a conflict here ... the equals() method doesn't know which one to do! So ... firstly, is object comparison something we wish to allow our users to do. I think it would be useful and equals() is a fundamental part of a well formed API. Not quite sure what the solution is right now though. Cheers, Jeremy On 15/11/2007, John Kaputin wrote: > With Woden M8 in progress and (hopefully) a Woden 1.0 release to follow we > need to think about stabilizing/finalizing the Woden API. The 1.0 release > should define our 'committed' API. Some API issues have been or are being > addressed via JIRAs. Some other issues may require more discussion on the > woden-dev mailing list before they're ready to track as JIRAs. > > To capture such issues and provide background info to prompt further > discussion, I have created an API Review page on the Woden Wiki [1]. See > the intro there for more details, read through the issues (2 so far) and > post your ideas to the list. > > [1] http://wiki.apache.org/ws/FrontPage/Woden/APIReview > > regards, > John Kaputin --------------------------------------------------------------------- To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org For additional commands, e-mail: woden-dev-help@ws.apache.org