axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: Expanding Java2wsdl to generate wsdd and classes
Date Wed, 16 Mar 2005 18:35:53 GMT
Jongjin,

Need to review the code first :) then we can decide if it can go into 1.2 final.

thx,
dims


On Thu, 17 Mar 2005 03:31:48 +0900, Choi Jongjin <gunsnroz@hotmail.com> wrote:
> Dear dims,
> 
> I like to see this feature included in Axis 1.2 final release.
> 
> I think this help the integration of beehive and other tools(like WebTools
> and my company's one)
> with Axis 1.2 final because it can give some kind of java -> wsdl -> java
> roundtripping feature.
> 
> If you have the burden of probably-not-proved new feature after RC3 and
> before final,
> can we limit the usage of it api only in Axis 1.2 final,
> and expose to java2wsdl class/ant later post Axis 1.2 final?
> 
> Axis 1.3 is too far for me.
> 
> /Jongjin
> 
> >From: Davanum Srinivas <davanum@gmail.com>
> >Reply-To: dims@apache.org
> >To: axis-dev@ws.apache.org
> >Subject: Re: Expanding Java2wsdl to generate wsdd and classes
> >Date: Wed, 16 Mar 2005 12:35:39 -0500
> >
> >+1 to file an enhancement....+1 to commit post 1.2 final release.
> >
> >-- dims
> >
> >
> >On Thu, 17 Mar 2005 02:15:47 +0900, Choi Jongjin <gunsnroz@hotmail.com>
> wrote:
> > > Hi, all.
> > >
> > > I suggest to expand java2wsdl to generate deploy.wsdd and required
> classes
> > > to deploy.
> > > There are several posts in axis-user list related to Axis/.NET interop
> and
> > > array handling.
> > >
> > > The recommendation for interop is "start-from-WSDL".
> > > "Start-from-WSDL" is good but there are cases where the users may/must
> > > start from Java classes.
> > >
> > > The current procedure for "start-from-Java" is :
> > >
> > > 1. write a java class
> > > 2. run 'java2wsdl'
> > > 3. run 'wsdl2java' with --server-side or other options using the
> generated
> > > wsdl of step 2 to get the wsdd and required classes (eg.
> ArrayOfXXX.java)
> > > 4. mix and match the java source/classes of step 1 and that of
> generated in
> > > step 3.
> > > 5. deploy the service
> > >
> > > If we can get the deploy.wsdd and required classes from java2wsdl with
> one
> > > step,
> > > the whole process may be simpler and it will free the user from writing
> > > error-prone hand-written deploy.wsdd in case of not running wsdl2java.
> > >
> > > I think that expanded java2wsdl may not need to have the all the
> options of
> > > current wsdl2java.
> > > Also the generated deploy.wsdd may need to some modification by hand to
> > > deploy in some cases. But the long 5 steps and the painful class
> mix/match
> > > can be removed.
> > >
> > > Also, I think this can ease the integration of Axis with other tools
> which
> > > use "start-from-Java" style of developement.
> > >
> > > I wrote the initial prototype with Axis 1.2RC3, and I feel that it is
> very
> > > useful for me.
> > > Unless there is a serious objection, I'll file it to JIRA (enhancement)
> and
> > > commit the patches once it is done clearly.
> > >
> > > Any opinion?
> > >
> > > Thanks.
> > >
> > > PS. The patch also includes the ArrayOfXXX <--> XXX[] conversion to
> keep
> > > the user's original source code on the server-side.
> > >
> > > /Jongjin
> > >
> > >
> >
> >
> >--
> >Davanum Srinivas - http://webservices.apache.org/~dims/
> 
> 


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

Mime
View raw message