You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsif-dev@ws.apache.org by Nirmal Mukhi <nm...@us.ibm.com> on 2003/02/10 14:23:01 UTC
Re: ws-commons / WSDL4J DIME extensions
Hi,
This would be a great start. I am particularly interested in refactoring
WSDL2Java and Java2WSDL to have a more pluggable architecture so we can
share common code more easily.
In the wsdl2java case we can refactor so that the common code works off
abstract wsdl only and allows you to plug in binding-specific code
generators. Axis can plug in code (currently mixed in with other wsdl2java
code) to operate on the SOAP binding and generate Axis stubs.
In the java2wsdl case we can do it similarly - have the common code
operate on java classes/interfaces to generate abstract WSDL, then plug in
code to add bindings to this. The SOAP binding plug in can also be part of
the common project since it's a standard binding, but this architecture
will let WSIF plug in code to generate java, EJB, JMS, J2C bindings which
are defined as a part of WSIF.
Nirmal.
Davanum Srinivas <di...@yahoo.com>
02/07/2003 11:19 AM
Please respond to axis-dev
To: axis-dev@ws.apache.org, wsif-dev@ws.apache.org, axis-dev
list <ax...@xml.apache.org>
cc:
Subject: Re: ws-commons / WSDL4J DIME extensions
Jeremy,
I got private emails saying that we could start something and that the
WSDL4J guys would pick them
up eventually.
FYI, I have already enhanced WSDL2Java with the minimum stuff needed for
us using the Unknown
Extensibility mechanism.
Let us do this...
1. start a proposal directory under your CVS module.
2. start coding there with a build.xml and generating a jar file that can
be dropped into both
axis and wsif.
3. Get the code to some good shape
4. Then use this code to start a ws-commons
What do you guys think with this approach? (don't want this code to be
like WSIL - with no
activity)
Thanks,
dims
--- Jeremy Hughes <hu...@hursley.ibm.com> wrote:
> Dims,
>
> You posted this to jsr110 mailing list ... did you eventually get a
> response? We have a todo in WSIF to write DIME WSDL4J extensions. ie. it
> doesn't have to be the WSDL4J project that implements this. Since this
would
> be useful to both WSIF and Axis projects perhaps we should think about a
> ws-commons project to hold this.
>
> org.apache.webservices.wsdl.extensions.dime.*
>
> What do you think?
>
> Jeremy
> Looks like no one wants to respond :(
>
> -- dims
>
> --- In jsr110-eg-disc@yahoogroups.com, "dims <di...@y...>" <di...@y...>
>
> wrote:
>
> > Folks,
>
> >
>
> > Apache Axis needs to support DIME (in our WSDL2Java
>
> > tool). Is there a plan to add support for DIME extensions (similar to
>
> > mime extensions) in WSDL4J?
>
> >
>
> > Thanks,
>
> > dims
>
> >
>
> > PS: WSDL's are at http://mssoapinterop.org/stkV3/. More details at
>
> > http://www.pocketsoap.com/interop/attachments.htm
>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Re: ws-commons / WSDL4J DIME extensions
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
hi,
i think that most pressing issue is that WSLD2Java AFAIK requires to
have binding in WSDL to generate code and for WSIF case we do not
need/require binding or service information during code generation but
we only want to generate code for portTypes/messages/operations/types ...
anyway it would be nice to have WSDL2Java modularized and name changed
to something more general than only Java code generation (WSDL2Code?).
thanks,
alek
Nirmal Mukhi wrote:
> This would be a great start. I am particularly interested in
> refactoring WSDL2Java and Java2WSDL to have a more pluggable
> architecture so we can share common code more easily.
>
> In the wsdl2java case we can refactor so that the common code works
> off abstract wsdl only and allows you to plug in binding-specific code
> generators. Axis can plug in code (currently mixed in with other
> wsdl2java code) to operate on the SOAP binding and generate Axis stubs.
>
> In the java2wsdl case we can do it similarly - have the common code
> operate on java classes/interfaces to generate abstract WSDL, then
> plug in code to add bindings to this. The SOAP binding plug in can
> also be part of the common project since it's a standard binding, but
> this architecture will let WSIF plug in code to generate java, EJB,
> JMS, J2C bindings which are defined as a part of WSIF.
>
> Nirmal.
>
>
>
> *Davanum Srinivas <di...@yahoo.com>*
>
> 02/07/2003 11:19 AM
> Please respond to axis-dev
>
>
> To: axis-dev@ws.apache.org, wsif-dev@ws.apache.org,
> axis-dev list <ax...@xml.apache.org>
> cc:
> Subject: Re: ws-commons / WSDL4J DIME extensions
>
>
>
>
> Jeremy,
>
> I got private emails saying that we could start something and that the
> WSDL4J guys would pick them
> up eventually.
>
> FYI, I have already enhanced WSDL2Java with the minimum stuff needed
> for us using the Unknown
> Extensibility mechanism.
>
> Let us do this...
> 1. start a proposal directory under your CVS module.
> 2. start coding there with a build.xml and generating a jar file that
> can be dropped into both
> axis and wsif.
> 3. Get the code to some good shape
> 4. Then use this code to start a ws-commons
>
> What do you guys think with this approach? (don't want this code to be
> like WSIL - with no
> activity)
>
> Thanks,
> dims
>
> --- Jeremy Hughes <hu...@hursley.ibm.com> wrote:
> > Dims,
> >
> > You posted this to jar110 mailing list ... did you eventually get a
> > response? We have a todo in WSIF to write DIME WSDL4J extensions. ie. it
> > doesn't have to be the WSDL4J project that implements this. Since
> this would
> > be useful to both WSIF and Axis projects perhaps we should think about a
> > ws-commons project to hold this.
> >
> > org.apache.webservices.wsdl.extensions.dime.*
> >
> > What do you think?
> >
> > Jeremy
> > Looks like no one wants to respond :(
> >
> > -- dims
> >
> > --- In jsr110-eg-disc@yahoogroups.com, "dims <di...@y...>" <di...@y...>
> >
> > wrote:
> >
> > > Folks,
> >
> > >
> >
> > > Apache Axis needs to support DIME (in our WSDL2Java
> >
> > > tool). Is there a plan to add support for DIME extensions (similar to
> >
> > > mime extensions) in WSDL4J?
> >
> > >
> >
> > > Thanks,
> >
> > > dims
> >
> > >
> >
> > > PS: WSDL's are at http://mssoapinterop.org/stkV3/. More details at
> >
> > > http://www.pocketsoap.com/interop/attachments.htm
> >
> >
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy.
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr
Re: ws-commons / WSDL4J DIME extensions
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
hi,
i think that most pressing issue is that WSLD2Java AFAIK requires to
have binding in WSDL to generate code and for WSIF case we do not
need/require binding or service information during code generation but
we only want to generate code for portTypes/messages/operations/types ...
anyway it would be nice to have WSDL2Java modularized and name changed
to something more general than only Java code generation (WSDL2Code?).
thanks,
alek
Nirmal Mukhi wrote:
> This would be a great start. I am particularly interested in
> refactoring WSDL2Java and Java2WSDL to have a more pluggable
> architecture so we can share common code more easily.
>
> In the wsdl2java case we can refactor so that the common code works
> off abstract wsdl only and allows you to plug in binding-specific code
> generators. Axis can plug in code (currently mixed in with other
> wsdl2java code) to operate on the SOAP binding and generate Axis stubs.
>
> In the java2wsdl case we can do it similarly - have the common code
> operate on java classes/interfaces to generate abstract WSDL, then
> plug in code to add bindings to this. The SOAP binding plug in can
> also be part of the common project since it's a standard binding, but
> this architecture will let WSIF plug in code to generate java, EJB,
> JMS, J2C bindings which are defined as a part of WSIF.
>
> Nirmal.
>
>
>
> *Davanum Srinivas <di...@yahoo.com>*
>
> 02/07/2003 11:19 AM
> Please respond to axis-dev
>
>
> To: axis-dev@ws.apache.org, wsif-dev@ws.apache.org,
> axis-dev list <ax...@xml.apache.org>
> cc:
> Subject: Re: ws-commons / WSDL4J DIME extensions
>
>
>
>
> Jeremy,
>
> I got private emails saying that we could start something and that the
> WSDL4J guys would pick them
> up eventually.
>
> FYI, I have already enhanced WSDL2Java with the minimum stuff needed
> for us using the Unknown
> Extensibility mechanism.
>
> Let us do this...
> 1. start a proposal directory under your CVS module.
> 2. start coding there with a build.xml and generating a jar file that
> can be dropped into both
> axis and wsif.
> 3. Get the code to some good shape
> 4. Then use this code to start a ws-commons
>
> What do you guys think with this approach? (don't want this code to be
> like WSIL - with no
> activity)
>
> Thanks,
> dims
>
> --- Jeremy Hughes <hu...@hursley.ibm.com> wrote:
> > Dims,
> >
> > You posted this to jar110 mailing list ... did you eventually get a
> > response? We have a todo in WSIF to write DIME WSDL4J extensions. ie. it
> > doesn't have to be the WSDL4J project that implements this. Since
> this would
> > be useful to both WSIF and Axis projects perhaps we should think about a
> > ws-commons project to hold this.
> >
> > org.apache.webservices.wsdl.extensions.dime.*
> >
> > What do you think?
> >
> > Jeremy
> > Looks like no one wants to respond :(
> >
> > -- dims
> >
> > --- In jsr110-eg-disc@yahoogroups.com, "dims <di...@y...>" <di...@y...>
> >
> > wrote:
> >
> > > Folks,
> >
> > >
> >
> > > Apache Axis needs to support DIME (in our WSDL2Java
> >
> > > tool). Is there a plan to add support for DIME extensions (similar to
> >
> > > mime extensions) in WSDL4J?
> >
> > >
> >
> > > Thanks,
> >
> > > dims
> >
> > >
> >
> > > PS: WSDL's are at http://mssoapinterop.org/stkV3/. More details at
> >
> > > http://www.pocketsoap.com/interop/attachments.htm
> >
> >
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
--
"Mr. Pauli, we in the audience are all agreed that your theory is crazy.
What divides us is whether it is crazy enough to be true." Niels H. D. Bohr