You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sagara Gunathunga (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 21:36:29 UTC

[jira] [Created] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

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 


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

--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Re: transportReceiver and AxisServlet

Posted by Nadir Amra <am...@us.ibm.com>.
Andreas,

Can one specify httpFrontendHostUrl multiple times (i.e. one for http and 
one for https)?

And what exactly should one specify for this parameter? Up to the context? 
(If this is documented somewhere please let me know.)

Thanks

Nadir Amra
Internet: amra@us.ibm.com

Andreas Veithen <an...@gmail.com> wrote on 03/28/2012 03:18:07 
PM:

> From: Andreas Veithen <an...@gmail.com>
> To: java-dev@axis.apache.org
> Date: 03/28/2012 03:31 PM
> Subject: Re: transportReceiver and AxisServlet
> 
> In that scenario, you should declare an http transport in axis2.xml
> and use the httpFrontendHostUrl parameter to configure the URLs
> exposed in the WSDL.
> 
> Andreas
> 
> On Wed, Mar 28, 2012 at 21:59, Nadir Amra <am...@us.ibm.com> wrote:
> > I have an HTTP server as a front-end to an application server contains
> > Axis2.   In the Axis2.XML file I have defined a transportReceiver for 
https.
> >  There is no transport receiver for http.
> >
> > I want to be able to by-pass the HTTP server and send requests to 
Axis2 over
> > http.  Currently, if I attempt to do this I get the following 
exception:
> >
> > AxisServlet: javax.servlet.ServletException: http is forbidden.
> >
> > I do not want to define a transport receiver for http because I do not 
want
> > http exposed in the WSDL files.
> >
> > Is there a way to do this?  And if not, do you think I should open a 
JIRA
> > requesting this support?  I would probably work on it to get it 
supported -
> > probably by simply adding a configuration variable in axis2.xml that
> > indicates that requests that do not have transport receivers should be
> > allowed - i.e. no exception should be thrown.
> >
> > Comments?
> >
> >
> > Nadir Amra
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
> 

Re: transportReceiver and AxisServlet

Posted by Andreas Veithen <an...@gmail.com>.
In that scenario, you should declare an http transport in axis2.xml
and use the httpFrontendHostUrl parameter to configure the URLs
exposed in the WSDL.

Andreas

On Wed, Mar 28, 2012 at 21:59, Nadir Amra <am...@us.ibm.com> wrote:
> I have an HTTP server as a front-end to an application server contains
> Axis2.   In the Axis2.XML file I have defined a transportReceiver for https.
>  There is no transport receiver for http.
>
> I want to be able to by-pass the HTTP server and send requests to Axis2 over
> http.  Currently, if I attempt to do this I get the following exception:
>
> AxisServlet: javax.servlet.ServletException: http is forbidden.
>
> I do not want to define a transport receiver for http because I do not want
> http exposed in the WSDL files.
>
> Is there a way to do this?  And if not, do you think I should open a JIRA
> requesting this support?  I would probably work on it to get it supported -
> probably by simply adding a configuration variable in axis2.xml that
> indicates that requests that do not have transport receivers should be
> allowed - i.e. no exception should be thrown.
>
> Comments?
>
>
> Nadir Amra

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


transportReceiver and AxisServlet

Posted by Nadir Amra <am...@us.ibm.com>.
I have an HTTP server as a front-end to an application server contains 
Axis2.   In the Axis2.XML file I have defined a transportReceiver for 
https.  There is no transport receiver for http. 

I want to be able to by-pass the HTTP server and send requests to Axis2 
over http.  Currently, if I attempt to do this I get the following 
exception:

AxisServlet: javax.servlet.ServletException: http is forbidden.

I do not want to define a transport receiver for http because I do not 
want http exposed in the WSDL files. 

Is there a way to do this?  And if not, do you think I should open a JIRA 
requesting this support?  I would probably work on it to get it supported 
- probably by simply adding a configuration variable in axis2.xml that 
indicates that requests that do not have transport receivers should be 
allowed - i.e. no exception should be thrown. 

Comments?


Nadir Amra

[jira] [Commented] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Sagara Gunathunga (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239241#comment-13239241 ] 

Sagara Gunathunga  commented on AXIS2-5279:
-------------------------------------------

As I mentioned in above issue description you don't need to work on all issues. There are 6 issues that have been mentioned as compulsory those are interdependent and you need to address them with clear designs and implementation approaches within your proposal. Other than that it is expected to resolve some of the issue that have been mentioned as optional tasks  that depends on your capacity and time availability.   

Since your are interested in this idea I would like to recommend you to go through those issues mentioned as optional and provide one or two patches before you start the project that will provide more insight on this project. Also this will add some positive points  to you during the selection process. Since you have previous experience with Woden IMO it's better to try out for few WSDL 2.0 related issue first.   
                
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Commented] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Ranjana Prasad (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406832#comment-13406832 ] 

Ranjana Prasad commented on AXIS2-5279:
---------------------------------------

Hi Sagara,

Please review attached patch which contains my progress so far.

Thanks, 

                
> 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
>         Attachments: WSDL-1.patch
>
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Updated] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Sagara Gunathunga (Updated) (JIRA)" <ji...@apache.org>.
     [ 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Commented] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Ranjana Prasad (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239150#comment-13239150 ] 

Ranjana Prasad commented on AXIS2-5279:
---------------------------------------

I would like to work on this issue as my GSoC project. I have some previous experience on Apache Woden project, I'm curious to know  do I have to fix all issues mentioned above ? Also any advice on proposal structure ?  
                
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Updated] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Ranjana Prasad (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ranjana Prasad updated AXIS2-5279:
----------------------------------

    Attachment: test-classes.patch

Sorry for inconvenience occurred. Please find attached patch for test classes. 
                
> 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
>         Attachments: WSDL-1.patch, test-classes.patch
>
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Updated] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Ranjana Prasad (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ranjana Prasad updated AXIS2-5279:
----------------------------------

    Attachment: wsdl2.patch.txt

Patch for WSDL 2.0 customization and test cases. 
                
> 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
>         Attachments: test-classes.patch, WSDL-1.patch, wsdl2.patch.txt
>
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Updated] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Ranjana Prasad (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ranjana Prasad updated AXIS2-5279:
----------------------------------

    Attachment: WSDL-1.patch
    
> 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
>         Attachments: WSDL-1.patch
>
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Commented] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Sagara Gunathunga (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408730#comment-13408730 ] 

Sagara Gunathunga  commented on AXIS2-5279:
-------------------------------------------

Provided patches available on r1358606. 
                
> 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
>         Attachments: WSDL-1.patch, test-classes.patch
>
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


[jira] [Commented] (AXIS2-5279) WSDL customization API for Axis2 and stabilize WSDL 2.0 features

Posted by "Sagara Gunathunga (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408670#comment-13408670 ] 

Sagara Gunathunga  commented on AXIS2-5279:
-------------------------------------------

Following test classes are missing in your patch please attach them.  

TestWSDL11SupplierTemplate
TestWSDL20Supplier
                
> 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
>         Attachments: WSDL-1.patch
>
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org