Return-Path: 
 <dev-return-50446-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 14202 invoked from network); 23 May 2007 12:26:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 May 2007 12:26:12 -0000
Received: (qmail 41218 invoked by uid 500); 23 May 2007 12:26:14 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 41161 invoked by uid 500); 23 May 2007 12:26:14 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 41147 invoked by uid 99); 23 May 2007 12:26:14 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 05:26:14 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of eljotpl@gmail.com designates
 64.233.162.239 as permitted sender)
Received: from [64.233.162.239] (HELO nz-out-0506.google.com) (64.233.162.239)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 05:26:07 -0700
Received: by nz-out-0506.google.com with SMTP id i11so84650nzh
        for <dev@geronimo.apache.org>; Wed, 23 May 2007 05:25:47 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=CfAlEzz8Swv8EdbJInwVfdQmiQ5J72MjhT9ZvQXs04y0faDpwJFqhR3gApXTg6EyUrkGED621dlQc7xdP4klAGbtP0QwxkxJmmsEXOv/+fVMaYEnDmSmpq9SVNCBw5CLmE9FtUXEvDJJhBXBRjKfMqyr59uEtmG6Ayz6+3yr/OY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=jhvjp+Ia2HzshTKBHh+ZyowfxD2iwDpWEOnuL737nVSlv0XM6B4p1NUUp9Xn4pl6BMykSsbcQDB+xYVjj8WOEfFtvehWuC+Yof5m0+RaFekeMbByLXdT1Unt11whhF4bIOjvKlJec9S4e2AbNrDLKdz9vojothLhhrJQGC97ymg=
Received: by 10.115.108.1 with SMTP id k1mr251568wam.1179923146628;
        Wed, 23 May 2007 05:25:46 -0700 (PDT)
Received: by 10.114.199.2 with HTTP; Wed, 23 May 2007 05:25:42 -0700 (PDT)
Message-ID: <1b5bfeb50705230525p5a6e036an218a12ea5ea91e2b@mail.gmail.com>
Date: Wed, 23 May 2007 14:25:42 +0200
From: "Jacek Laskowski" <jacek@laskowski.net.pl>
Reply-To: jacek@laskowski.net.pl
Sender: eljotpl@gmail.com
To: dev@geronimo.apache.org
Subject: Re: Do we still need sun's jaxws-api.jar?
In-Reply-To: <4652FEB5.2000702@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4652FEB5.2000702@gmail.com>
X-Google-Sender-Auth: c378864442dbac63
X-Virus-Checked: Checked by ClamAV on apache.org

On 5/22/07, Lin Sun <linsun.unc@gmail.com> wrote:

> I saw that we still use sun's jaxws-api in root pom.xml, jee-spec
> pom.xml, and a few webservices test.
>
>          <dependency>
>              <groupId>javax.xml.ws</groupId>
>              <artifactId>jaxws-api</artifactId>
>          </dependency>
>
> I was under the impression both CXF and Axis2 use axis2's jaxws-api.  If
> so, can I remove/replace all the reference of sun's jaxws-api w/ axis2's
> jaxws-api?

If G works fine after doing so, I'd say go ahead. I wonder why you're
concerned with it? Is Axis2 JAXWS-API impl better than Sun's?

It may impact the TCK effort so before you go for it send an email
here with an appropriate subject so people don't get p..sed off when
unexpected happens (you know, don't push Jason to his limits ;-))

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl