+1. Let's do it :) On 1/4/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > On Wed, 2006-01-04 at 17:37 -0500, Davanum Srinivas wrote: > > Folks, > > > > I've checked in a few changes to generated code and wanted to give you > > all an update. With the current SVN, here's what you can do. > > Excellent! > > > 1. Add the axis2 jar and all dependent jars to CLASSPATH > > HINT: if you run "maven create-lib" it will create a directory > > target/lib with all the dependency jars > > > > 2. Run WSDL2Java against say the perf.wsdl in SVN > > HINT: I use "java org.apache.axis2.wsdl.WSDL2Java -d adb -o work > > -s -p samples.perf -t -ss -sd -uri > > \APACHE\axis2\modules\samples\wsdl\perf.wsdl", this will create all > > the generated code under a new directory named work. > > If these WSDL2Java options are the right ones for the common case, can > we set them as defaults? Ideally, IMO, to generate a stub literally I > should have to type "WSDL2Java foo.wsdl" and that's it. In that case, > IMO, we should generate exactly one foo.java for the entire stub in the > current directory. Maybe no build.xml even: if I was able to run > WSDL2Java at all then I had the classpath right in the first place .. so > compiling should be simply a matter typing javac foo.java, no? > > To do the client and server both then of course we need more stuff .. so > maybe another combination of behaviors? > > Basically I'm pushing for making intelligent choices for defaults for > the 17 options of WSDL2Java. > > Sanjiva. > >
-- Davanum Srinivas : http://wso2.com/blogs/
