axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <>
Subject RE: Support needed for conditional stub/skeleton generation
Date Wed, 18 Feb 2004 19:52:03 GMT


Wouldn't this be implemented as a switch to the command line WSDL2Java?

--nobeans - turns off generation of JavaBeans for Schema types.

This would prevent us from generating code that you don't want.

Many users generate code in a directory, and then copy only the classes they
want and need to their build directories.  This gives maximum control over
what generated artifacts are used.

I seem to be missing why this seems much more complicated that I think it

All that being said, we welcome your enhancements to WSDL2Java and its ant
tasks.  I would like to see some good documentation on the 'how' and 'why'
of the changes you describe go in to our tree at the same time the changes
go in.

Tom Jordahl
Macromedia Server Development

-----Original Message-----
From: Jim Stafford [] 
Sent: Wednesday, February 18, 2004 1:49 PM
To: Axis Developer
Subject: Support needed for conditional stub/skeleton generation

We would like to have the ability to use our externally created beans 
passed as data parameters within the WSDL->Java generated static 
stub/skeletons. We understand and have addressed all the issues involved 
with setting up serializers and deserializers, etc. However, there seems 
to be a deficiency in the implementation of the WSDL to Java generation. 
You cannot keep the WSDL to Java generation process from generating 
classes passed by the generated interfaces in the current CVS code base. 
There is a flag to turn off code generation for imported WSDL files, but 
that fails. There is the ability to identify a custom 
JavaGenerationFactory, but it cannot be passed any state information 
though the Ant task.

I have finished implementing a local changes to the CVS version of 
org.apache.axis.wsdl.toJava and packages. 
Namely I have changed (added the ability to 
specify includes/excludes and general propeties as a factory 
sub-element), (added the ability to carry the more robust 
factory properties), extended JavaGenerationFactory (added the ability 
to assign the NoopGenerator for identified namespaces), and added some 
bean classes to carry the factory specification.

Here's an example of our common Ant task:
<axis-wsdl2java url="${wsdl.dir}/${ws.file}"    ...    >
   <mapping namespace="${ws.namespace1}"
   <factory classname="${factory}">
       <exclude namespace="${ws.namespace1}"/>

We are using this change locally and are happy with it. I need to write 
up some JUnit test cases before submitting it (I assume). I may also 
make a few more modifications (create Factory Methods in to make it easier to extend). However, I wanted to 
announce my need and intent to see what comments might be involved 
before submitting the bug/enhacement request and CVS Patch file.

Any comments? any suggestions?


View raw message