beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "daryoush mehrtash (JIRA)" <>
Subject [jira] Commented: (BEEHIVE-782) create Ant task for generating a web service control
Date Thu, 02 Jun 2005 17:23:00 GMT
     [ ]
daryoush mehrtash commented on BEEHIVE-782:

Currently generating a SC is a two step process, 1) create the types, 2) run extension maker.
  For literal WSDLs XMLBean is the preferred type generation tool, and for the RPC-Encoded
Axis type generators must be used.    I think the Ant task that is proposed here should also
examine the WSDL and generate the types also.  This would simplify our build process.  We
should also have a flag for disabling type generation so that a developer can use his/her
own type generation.

> create Ant task for generating a web service control
> ----------------------------------------------------
>          Key: BEEHIVE-782
>          URL:
>      Project: Beehive
>         Type: New Feature
>   Components: Controls
>     Versions: V1Alpha, V1Beta, V1, TBD
>     Reporter: Eddie O'Neil
>      Fix For: TBD

> Currently, the Java class ExtensionMaker is used to generate a web service control, and
it is called from an Ant build as something like:
> 		<java classname="org.apache.beehive.controls.system.webservice.generator.ExtensionMaker">
> 			<classpath>
> 				<path refid="build.classpath" />
> 				<pathelement location="${build.classes}" />
> 			</classpath>
> 			<arg line="-gen_root ${gen.source.dir} 
> 		      	-wsdl ${schema.dir}
> 		      	-pkg ${my.service.control.package}" />
> 		</java>
> It would be quite useful to provide an Ant task that does the same thing with a cleaner
Ant API like:
>   <generateServiceControl srcdestdir="${gen.src.dir}" 
>                           wsdl="${schema.dir}"
>                           outputpackage="${my.service.control.package}"/>
> -- or something similar :).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message