Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of kentaminator@gmail.com
 designates 64.233.184.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=LxEwzz4MQDnp727U9KWAvoYu3/0RgF4QaZl6437DOg1r/ricrxzj4ykvU9gmjm0i22T9zHr0aeZeOpUpg0ExCJJqHXKfNzVerFXIgl4xBeUuGr9mBYWs6b0z5KXuBacrQC9vWDG9w4bvyOMgFUHicOVyzNIcwZPFvBok282xN6o=
Message-ID: <e52f74f80603241739g15d707afu26cfb696de801a72@mail.gmail.com>
Date: Fri, 24 Mar 2006 17:39:28 -0800
From: "Kenneth Tam" <kentaminator@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?
In-Reply-To: <f43ea5790603142207j233faaas9d2f511a6e799c85@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <e52f74f80603141540l1b1ee1e6r812ae751dbca549e@mail.gmail.com>
	 <f43ea5790603142207j233faaas9d2f511a6e799c85@mail.gmail.com>

Hi folks,

So after looking at this a little more, it seems that separating the
JAX-B dependency from JAX-WS isn't really practical.  I'm playing with
leveraging the JAXB2 RI, rather than waiting for an ASL licensed impl
-- the RI's JAXBModel interface & associated type model seems readily
usable.  This would require a binary-only dependency on the JAXB2 RI,
which is CDDL.

Thoughts on whether this is an acceptable approach?  If accepted, the
current license policy proposal being discussed in legal would
explicitly permit such a dependency; in the meantime, I know
ServiceMix has this dependency as well and appear to be quite happily
proceeding along with it until it's been declared to be clearly
problematic :)

On 3/14/06, Ajith Ranabahu <ajith.ranabahu@gmail.com> wrote:
> Hi all,
> Exactly. You can reuse most of the writer/emitter stuff but
> essentially what you'll have to implement is an emitter and a bunch of
> templates. "jax-ws" is fine for the lang name.
>
> Ajith
>
> On 3/15/06, Kenneth Tam <kentaminator@gmail.com> wrote:
> > Looking at WSDL -> Java work required by JAX-WS, and one way that
> > occurred to me to do this was to define another "language" ("jax-ws")
> > as a peer to "java" and "csharp", for which there would be an emitter
> > & associated templates/writer classes.  This implies that the "java"
> > language option is really the codegen for native Axis2 API stuff in
> > Java.
> >
> > Thoughts?
> >
> > On 2/15/06, Afkham Azeez <afkham@gmail.com> wrote:
> > > Hi Kenneth,
> > > Actually only the JAX-WS interfaces have been added to the AXIS2
> > > project as the jaxws module. No real work has been started on this
> > > module yet. We are planning to start on this in the near future. Your
> > > participation and suggestions are welcome.
> > >
> > > Regards
> > > Azeez
> > >
> > > On 2/16/06, Kenneth Tam <kentaminator@gmail.com> wrote:
> > > > Hi folks,
> > > >
> > > > Is the JAX-WS work for Axis2 being done in a public sandbox?   I kn=
ow
> > > > this isn't a priority for the 1.0 release, but the mailing list
> > > > archives indicate there are some rumblings on getting it going.
> > > > Afkham, I see the JIRA issue re: JAX-WS implementation is assigned =
to
> > > > you -- would love to hear your thoughts on how you were planning to=
 go
> > > > about the work.
> > > >
> > > > thanks!
> > > > k
> > > >
> > >
> > >
> > > --
> > > Thanks
> > > Afkham Azeez
> > >
> >
>
>
> --
> Ajith Ranabahu
>