[
https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga updated AXIS2-5279:
--------------------------------------
Description:
This project idea consists of collection of Axis2 issues related to WSDL
features and mainly focus on following two areas.
1.) Introduce a API to customize default WSDL generation behavior of Axis2 and
this need to be supported to both WSDL 1.1 and WSDL 2.0.
2.) Stabilize WSDL 2.0 features and add missing features.
Following are the set of issues that have been identified as compulsory tasks
of this project and required to provide detailed technical design with
proposals.
AXIS2-3492 - WSDLSupplier configuration and/or check is not proper/obvious
AXIS2-5278 - WSDLSupplier should support for both WSDL 1.1 and WSDL 2.0
AXIS2-3653 - customization of dynamic WSDL creation
AXIS2-5240 - Provide an API/mechanism for setting parameters for run-time
Java2WSDL generation.
AXIS2-3114 - Control what wsdl bindings returned via services.xml
AXIS2-5191 - Axis2 should support to use "useOriginalWSDL" property for WSDL
2.0
Further following are some of the optional tasks identified and it's expected
to complete some of those issues as well ( Not required to fix following
complete list of issues).
AXIS2-4976 - Axis2 wsdl2code code generation bug caused by "localName"
AXIS2-4407 - Axis 2 does not pick up wsdl2.0 which is modified to include
whttp:location and whttp:method for Restful services
AXIS2-4193 - WSDL2JAVA no setters in ADBBean
AXIS2-3768 - WSDL20ToAxisServiceBuilder does not read policies in WSDL 2.0 docs
AXIS2-3108 - Broken WSDL for operations added by modules
AXIS2-4734 - Issue with schema import in the wsdl file
AXIS2-4985 - NullPointerException in axis2-aar-maven-plugin if no fileSet is
specified
AXIS2-4747 - Possible bug when generating code for livebookings wsdl
AXIS2-4521 - WSDL504,Could not locate the schema document when tomcat starts up
AXIS2-4436 - Woden attempts to load http://www.w3.org/2001/XMLSchema.xsd every
time it parses a WSDL document (or if Axis2 instructs Woden to do so)
AXIS2-4978 - Copying data from inputStream to OuputStream needs appropriate
buffer size
AXIS2-4065 - Policy attached to an input operation in a WSDL does not get
copied to the Stub operation by WSDL2Java
was:
This project idea consists of collection of Axis2 issues related to WSDL
features and mainly focus on following two areas.
1.) Introduce a API to customize default WSDL generation behavior of Axis2 and
this need to be supported to both WSDL 1.1 and WSDL 2.0.
2.) Stabilize WSDL 2.0 features and add missing features.
Following are the set of issues that have been identified as compulsory tasks
of this project and required to provide detailed technical design with
proposals.
AXIS2-3492 - WSDLSupplier configuration and/or check is not proper/obvious
AXIS2-5278 - WSDLSupplier should support for both WSDL 1.1 and WSDL 2.0
AXIS2-3653 - customization of dynamic WSDL creation
AXIS2-5240 - Provide an API/mechanism for setting parameters for run-time
Java2WSDL generation.
AXIS2-3114 - Control what wsdl bindings returned via services.xml
AXIS2-5191 - Axis2 should support to use "useOriginalWSDL" property for WSDL
2.0
> WSDL customization API for Axis2 and stabilize WSDL 2.0 features
> -----------------------------------------------------------------
>
> Key: AXIS2-5279
> URL: https://issues.apache.org/jira/browse/AXIS2-5279
> Project: Axis2
> Issue Type: Improvement
> Reporter: Sagara Gunathunga
> Labels: axis-gsoc, gsoc2012
>
> This project idea consists of collection of Axis2 issues related to WSDL
> features and mainly focus on following two areas.
> 1.) Introduce a API to customize default WSDL generation behavior of Axis2
> and this need to be supported to both WSDL 1.1 and WSDL 2.0.
> 2.) Stabilize WSDL 2.0 features and add missing features.
> Following are the set of issues that have been identified as compulsory tasks
> of this project and required to provide detailed technical design with
> proposals.
> AXIS2-3492 - WSDLSupplier configuration and/or check is not proper/obvious
> AXIS2-5278 - WSDLSupplier should support for both WSDL 1.1 and WSDL 2.0
> AXIS2-3653 - customization of dynamic WSDL creation
> AXIS2-5240 - Provide an API/mechanism for setting parameters for run-time
> Java2WSDL generation.
> AXIS2-3114 - Control what wsdl bindings returned via services.xml
> AXIS2-5191 - Axis2 should support to use "useOriginalWSDL" property for
> WSDL 2.0
> Further following are some of the optional tasks identified and it's expected
> to complete some of those issues as well ( Not required to fix following
> complete list of issues).
> AXIS2-4976 - Axis2 wsdl2code code generation bug caused by "localName"
> AXIS2-4407 - Axis 2 does not pick up wsdl2.0 which is modified to include
> whttp:location and whttp:method for Restful services
> AXIS2-4193 - WSDL2JAVA no setters in ADBBean
> AXIS2-3768 - WSDL20ToAxisServiceBuilder does not read policies in WSDL 2.0
> docs
> AXIS2-3108 - Broken WSDL for operations added by modules
> AXIS2-4734 - Issue with schema import in the wsdl file
> AXIS2-4985 - NullPointerException in axis2-aar-maven-plugin if no fileSet is
> specified
> AXIS2-4747 - Possible bug when generating code for livebookings wsdl
> AXIS2-4521 - WSDL504,Could not locate the schema document when tomcat starts
> up
> AXIS2-4436 - Woden attempts to load http://www.w3.org/2001/XMLSchema.xsd
> every time it parses a WSDL document (or if Axis2 instructs Woden to do so)
> AXIS2-4978 - Copying data from inputStream to OuputStream needs appropriate
> buffer size
> AXIS2-4065 - Policy attached to an input operation in a WSDL does not get
> copied to the Stub operation by WSDL2Java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
