You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Kenneth Tam <ke...@gmail.com> on 2006/03/15 00:40:23 UTC
Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?
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 <af...@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 <ke...@gmail.com> wrote:
> > Hi folks,
> >
> > Is the JAX-WS work for Axis2 being done in a public sandbox? I know
> > 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
>
Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?
Posted by Davanum Srinivas <da...@gmail.com>.
JWSDP is CDDL, GlassFish is CDDL...Should we pack up our bags? :)
Geronimo needs a JAXB Impl not just us. Not taking a JAXB RI
dependency forces us to think more than give up. Let's ask around, may
be someone has some resources that we can redirect to JaxMe to bring
it up to JAXB2. I am not going to comment on ServiceMix's approach as
i am not a mentor or a participant there.
BTW, there is already some code in the current SVN that calls JaxMe's
schema to java generator. Not sure if the generated code works, IMHO,
but getting that working that would be first step.
thanks,
dims
On 3/24/06, Kenneth Tam <ke...@gmail.com> wrote:
> 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 <aj...@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 <ke...@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 <af...@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 <ke...@gmail.com> wrote:
> > > > > Hi folks,
> > > > >
> > > > > Is the JAX-WS work for Axis2 being done in a public sandbox? I know
> > > > > 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
> >
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?
Posted by Kenneth Tam <ke...@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 <aj...@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 <ke...@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 <af...@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 <ke...@gmail.com> wrote:
> > > > Hi folks,
> > > >
> > > > Is the JAX-WS work for Axis2 being done in a public sandbox? I know
> > > > 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
>
Re: [Axis2] JAX-WS as another WSDL2Code/Java language option?
Posted by Ajith Ranabahu <aj...@gmail.com>.
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 <ke...@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 <af...@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 <ke...@gmail.com> wrote:
> > > Hi folks,
> > >
> > > Is the JAX-WS work for Axis2 being done in a public sandbox? I know
> > > 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