You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by hanasaki jiji <ha...@gmail.com> on 2009/03/01 01:30:14 UTC
howto generate WSDL for all services in a project? howto generate
Java from all WSDL in a project
http://cwiki.apache.org/CXF20DOC/maven-integration-and-plugin.html
= WSDL2Java
After looking at the above link, it appears that each webservice =>
Java generation must have an explicit POM.xml update for a new line
containing the WSDL. Is there any way to have maven scan all its
project directories (or a pattern of directories) and generate source
for all WSDL files found?
== Java2WSDL
After looking at the above link, it appears that each Java => WSDL
generation must have an explicit POM.xml update for a new line
containing the fully qualified class name from which the WSDL will be
genrrated. Is there any way to have maven scan all its project
directories (or a pattern of directories) and generate WSDL for all
Java files found? Can this be done with just classnames and the
annotation metadata in them without source available?
Thank you in advance!
Re: howto generate WSDL for all services in a project? howto generate Java from all WSDL in a project
Posted by Daniel Kulp <dk...@apache.org>.
On Sat February 28 2009 7:30:14 pm hanasaki jiji wrote:
> http://cwiki.apache.org/CXF20DOC/maven-integration-and-plugin.html
>
> = WSDL2Java
> After looking at the above link, it appears that each webservice =>
> Java generation must have an explicit POM.xml update for a new line
> containing the WSDL. Is there any way to have maven scan all its
> project directories (or a pattern of directories) and generate source
> for all WSDL files found?
With 2.1, the plugin allows generating code for all the wsdl's in a single
directory. All the wsdl's you stick in src/main/resources/wsdl get
processed. ALternatively, add the wsdlRoot param to the plugin to change the
directory to something else. It doesn't scan everything though.
Feel free to log a jira, and a patch would be nice as well. :-)
> == Java2WSDL
> After looking at the above link, it appears that each Java => WSDL
> generation must have an explicit POM.xml update for a new line
> containing the fully qualified class name from which the WSDL will be
> genrrated. Is there any way to have maven scan all its project
> directories (or a pattern of directories) and generate WSDL for all
> Java files found? Can this be done with just classnames and the
> annotation metadata in them without source available?
Not right now. Log a jira (and a patch). :-)
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog