WSDL2Java is already pluggable. This work
was done by the guys from IBM (who apparently vanished from the face of the
Internet after 1.0 shipped).
See the WSD2 class and the factories for
each of the WSDL top level elements. All of the Java* emitters can be replaced
with your favorite language without too much trouble.
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Nirmal Mukhi
[mailto:[EMAIL PROTECTED]]
Sent: Monday, February 10, 2003
8:23 AM
To: axis-dev list;
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: 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
<[EMAIL PROTECTED]>
02/07/2003 11:19 AM
Please
respond to axis-dev
|
To: [EMAIL PROTECTED],
[EMAIL PROTECTED], axis-dev list <[EMAIL PROTECTED]>
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 <[EMAIL PROTECTED]>
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 [EMAIL PROTECTED],
"dims <[EMAIL PROTECTED]>" <[EMAIL PROTECTED]>
>
> 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
