You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2007/04/12 15:57:32 UTC
[jira] Created: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
-------------------------------------------------------------------------------
Key: GERONIMO-3092
URL: https://issues.apache.org/jira/browse/GERONIMO-3092
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.
[jira] Commented: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488390 ]
Lin Sun commented on GERONIMO-3092:
-----------------------------------
Chatted with dims a bit on IRC. Looks like if the servicename is provided in webservices.xml, we can pass it onto wsgen so it can generate the wsdl file based on the servicename. In that case, we don't need to scan the directory. Otherwise, we'll scan the directory and return the first wsdl file we find.
one thing unclear is whether the servicename or portname specified in webservices.xml should win over what is specified in annotation. If so, we should pass the servicename and portname to wsgen when they exists in webservices.xml. Otherwise, we shouldn't.
Lin
> Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
> -------------------------------------------------------------------------------
>
> Key: GERONIMO-3092
> URL: https://issues.apache.org/jira/browse/GERONIMO-3092
> 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.
[jira] Assigned: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun reassigned GERONIMO-3092:
---------------------------------
Assignee: (was: Lin Sun)
unassign it so that a committer can review it...:)
> Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
> -------------------------------------------------------------------------------
>
> Key: GERONIMO-3092
> URL: https://issues.apache.org/jira/browse/GERONIMO-3092
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0-M5
> Reporter: Lin Sun
> Fix For: 2.0-M5
>
> Attachments: G3092.patch
>
>
> 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.
[jira] Closed: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun closed GERONIMO-3092.
-----------------------------
this has been checked in and seems working well
> Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
> -------------------------------------------------------------------------------
>
> Key: GERONIMO-3092
> URL: https://issues.apache.org/jira/browse/GERONIMO-3092
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0-M5
> Reporter: Lin Sun
> Fix For: 2.0-M5
>
> Attachments: G3092.patch
>
>
> 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.
[jira] Updated: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun updated GERONIMO-3092:
------------------------------
Attachment: G3092.patch
Tested with the cases where servicename and portname exist in webservices.xml or webservices.xml isn't provided.
> Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
> -------------------------------------------------------------------------------
>
> Key: GERONIMO-3092
> URL: https://issues.apache.org/jira/browse/GERONIMO-3092
> 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
>
> Attachments: G3092.patch
>
>
> 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.
[jira] Commented: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488401 ]
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 annotation.
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: https://issues.apache.org/jira/browse/GERONIMO-3092
> 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.
[jira] Resolved: (GERONIMO-3092) Axis2: after wsgen tool, need to
scan the directory for the generated wsdl file
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved GERONIMO-3092.
----------------------------------------
Resolution: Fixed
Fixed in svn revision 528250
thanks,
dims
> Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
> -------------------------------------------------------------------------------
>
> Key: GERONIMO-3092
> URL: https://issues.apache.org/jira/browse/GERONIMO-3092
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0-M5
> Reporter: Lin Sun
> Fix For: 2.0-M5
>
> Attachments: G3092.patch
>
>
> 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.