You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Anthony Fox <an...@gmail.com> on 2005/08/30 15:24:35 UTC

autogenerating wsdd

Hi,

I've searched for a response to the following question but have not
found anything satisfactory, so apologies if it has been discussed
previously.  I need a tool that will autogenerate wsdd as part of an
ant build process.  Currently, I run java2wsdl on the interface that I
am trying to expose and then run wsdl2java on the generated wsdl to
generate the wsdd.  I throw away the generated source as I won't be
needing it.  The problem is that the package to namespace to package
mapping across the use of the two tools loses something in the
translation.  java2wsdl maps all packages like com.mycompany.myproject
to http://myproject.mycompany.com which wsdl2java in turn maps my
input and output types to java:myproject.mycompany.com.  I just want
my deployed service to use the appropriate classes that I have already
written.  I can get around this problem by providing all the
appropriate package to namespace mappings and subsequent namespace to
package mappings, however, I won't know the packages used during the
build process.  Is there a switch to java2wsdl that maps all packages
to xml namespaces of the same string?  Is there something similar to
NStoPkg.properties that I can provide to java2wsdl?

Thanks,
Anthony