geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3092) Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
Date Thu, 12 Apr 2007 15:20:32 GMT


Lin Sun commented on GERONIMO-3092:

Per JSR109 sec 7.1.1:

The webservices.xml deployment descriptor file defines the set of Web services that are to
be deployed in
a Web Services for Java EE enabled container. With JAX-WS the use of webservices.xml is optional
since the annotations can be used to specify most of the information specified in this deployment
descriptor file.
The deployment descriptors are only used to override or augment the annotation member attributes.

If you seach for override, the spec also gives different examples such as how <wsdl-file>
should overwrite wsdlLocation in annotation and how <handlerchain> overwrites the handlerchain

so the <servicename> and <portname> in webservices.xml should win, if they exist
or webservices.xml exists.

> Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
> -------------------------------------------------------------------------------
>                 Key: GERONIMO-3092
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0-M5
>            Reporter: Lin Sun
>         Assigned To: Lin Sun
>             Fix For: 2.0-M5
> Currently it is looking for SOAPService.wsdl.  Later on I found out the tool is generating
wsdl file's name based on the serviceName specified in the webservice annotation of the SEIC.
  For example, for jaxws-war we have:
> @WebService(serviceName = "SOAPService",
> A solution could be to scan any wsdl file in the output directory.  

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message