Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <19e0530f040819182819c0e47c@mail.gmail.com>
Date: Fri, 20 Aug 2004 06:58:35 +0530
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: Beehive Developers <beehive-dev@incubator.apache.org>
Subject: Re: JSR-181 JWS file extensions: .jws vs .java
Cc: axis-dev@ws.apache.org
In-Reply-To: <4B2B4C417991364996F035E1EE39E2E101B8EB7E@uskiex01.amer.bea.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <4B2B4C417991364996F035E1EE39E2E101B8EB7E@uskiex01.amer.bea.com>

let's support both :)

-- dims

On Thu, 19 Aug 2004 17:22:58 -0700, Michael Merz <mmerz@bea.com> wrote:
> 
> 
> Hi all,
> 
> Axis 1.x expects Java Web Service files to have a ".jws" extension. This
> certainly makes sense, since there Axis can't differentiate between Java
> Web Service files and regular Java files just by looking at their
> contents.
> 
> JSR-181, however, makes additional information available in form of
> metadata (annotations). With this additional information it is now
> possible to tell Java Web Service source files apart from regular Java
> source files -- just by looking at the files' contents; thus, the ".jws"
> extension is not necessary anymore.
> 
> Since Java Web Service source files are Java files, I suggest to get rid
> of the ".jws" extension altogether and to support the standard ".java"
> extension for Java Web Service files.
> 
> Comments? Opinions?
> 
> Cheers,
> 
> -michael
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/