Return-Path: 
 <axis-dev-return-40801-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 17742 invoked from network); 6 Dec 2005 21:21:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 6 Dec 2005 21:21:43 -0000
Received: (qmail 50720 invoked by uid 500); 6 Dec 2005 21:20:45 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 50663 invoked by uid 500); 6 Dec 2005 21:20:45 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 50635 invoked by uid 99); 6 Dec 2005 21:20:45 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2005 13:20:45 -0800
X-ASF-Spam-Status: No, hits=0.7 required=10.0
	tests=DATE_IN_PAST_06_12
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [194.250.131.236] (HELO smtp-wifi.orange.fr) (194.250.131.236)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2005 13:20:44 -0800
Received: from [172.23.172.239] (81.253.64.42) by smtp-wifi.orange.fr
 (7.0.031.3)
        id 41628E4300189B5A for axis-dev@ws.apache.org;
 Tue, 6 Dec 2005 22:26:30 +0100
Subject: Re: [Axis2] Configuration hierarchy no longer extends the
	WSDLComponents !
From: Sanjiva Weerawarana <sanjiva@opensource.lk>
To: axis-dev@ws.apache.org
In-Reply-To: <3ce57c850512031932m15d3e399j459d3d39ba5c06ff@mail.gmail.com>
References: <3ce57c850512031932m15d3e399j459d3d39ba5c06ff@mail.gmail.com>
Content-Type: text/plain
Organization: Lanka Software Foundation
Date: Tue, 06 Dec 2005 19:21:10 +0600
Message-Id: <1133875270.21103.76.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.1.1 
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

Hi Chathura!

> I was just observing that we no longer extend our Configuration (or
> Axis* , AxisOperation, etc) from the relevant WSDL component.
> eg AxisOperation (use to) extends WSDLOperation.
> 
> I thought that was a nice thing to do because our WOM builder has the
> flexibility of building objects out of factory. That is you can ask
> the WOM builder to build a AxisOperation object rather than a
> WSDLOperation by registering a (AxisDescWSDLComponentFactory). IMO it
> is a cleaner way to build the configuration objects rather than
> keeping the object inside and delegating ALL the methods which it does
> right now.
> 
> Is there any good reason why we did this change?

Sure :) ... how about because it was *never* used as the relevant WSDL
component? Other than that, there's a mismatch too .. we currently tag
AxisService as implementing WSDLService. But that's not really true - an
AxisService represents the entire service, not just the <service>
element. OTOH AxisOperation may have info that may have come from both
portType/operation and binding/operation .. so its not a perfect match,

Also, we created WOM as a start towards a WSDL2 component model.
Unfortunately Woden didn't take over and use that stuff .. so right now
WOM works as a WSDL representation which is independent of WSDL 1.1 and
WSDL 2.0. We could in theory remove WOM IMO but it'll require a huge
amount of work because even the codegen stuff uses it heavily. So I'm
not for doing that work now .. its a potential refactoring that could be
considered after Woden ships and we really have 2 true WSDL models
available to deal with.

What are the arguments for keeping it?

Sanjiva.