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 "Sanka Samaranayake (JIRA)" <ji...@apache.org> on 2008/03/28 13:06:24 UTC

[jira] Created: (AXIS2-3677) Suggested fixes for 1.4 RC3

Suggested fixes for 1.4 RC3
---------------------------

                 Key: AXIS2-3677
                 URL: https://issues.apache.org/jira/browse/AXIS2-3677
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
            Reporter: Sanka Samaranayake
            Assignee: Sanka Samaranayake
            Priority: Critical
         Attachments: suggested-changes-rc2.patch

I really like to include the attached patch in rc3 which contains following fixes

a) Binding Message Level Dispatching -- a minor fix which set the target Axis binding message in the message context.

b) Minor fix which set policies in the appropriate element of the generated WSDL based on the Axis Service and Axis Service Binding hierarchy.

c) Support for policy attachments at binding level -- this is a feature that  I would really like to see in Axis2 1.4 release. It allows the user to add <wsp:PolicyAttachment> element in the services.xml and specify policies that applicable bindings. This very useful since it provides a way for the service authors to specify policies for specific bindings. (Some polices are only meaningful at binding level (.e.g security) and at the moment this can be done only by including a WSDL in service archive file)

NOTE: 
1) There are one test failure in JAXWS Integration , and three failures in the integration modules. I will fix them and submit another patch ASAP



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


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


[jira] Updated: (AXIS2-3677) Suggested fixes for 1.4 RC3

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

Davanum Srinivas updated AXIS2-3677:
------------------------------------

    Fix Version/s: 1.4

> Suggested fixes for 1.4 RC3
> ---------------------------
>
>                 Key: AXIS2-3677
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3677
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Sanka Samaranayake
>            Assignee: Sanka Samaranayake
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: suggested-changes-rc2.patch
>
>
> I really like to include the attached patch in rc3 which contains following fixes
> a) Binding Message Level Dispatching -- a minor fix which set the target Axis binding message in the message context.
> b) Minor fix which set policies in the appropriate element of the generated WSDL based on the Axis Service and Axis Service Binding hierarchy.
> c) Support for policy attachments at binding level -- this is a feature that  I would really like to see in Axis2 1.4 release. It allows the user to add <wsp:PolicyAttachment> element in the services.xml and specify policies that applicable bindings. This very useful since it provides a way for the service authors to specify policies for specific bindings. (Some polices are only meaningful at binding level (.e.g security) and at the moment this can be done only by including a WSDL in service archive file)
> NOTE: 
> 1) There are one test failure in JAXWS Integration , and three failures in the integration modules. I will fix them and submit another patch ASAP

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


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


[jira] Updated: (AXIS2-3677) Suggested fixes for 1.4 RC3

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

Sanka Samaranayake updated AXIS2-3677:
--------------------------------------

    Attachment: suggested-changes-rc2.patch

> Suggested fixes for 1.4 RC3
> ---------------------------
>
>                 Key: AXIS2-3677
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3677
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Sanka Samaranayake
>            Assignee: Sanka Samaranayake
>            Priority: Critical
>         Attachments: suggested-changes-rc2.patch
>
>
> I really like to include the attached patch in rc3 which contains following fixes
> a) Binding Message Level Dispatching -- a minor fix which set the target Axis binding message in the message context.
> b) Minor fix which set policies in the appropriate element of the generated WSDL based on the Axis Service and Axis Service Binding hierarchy.
> c) Support for policy attachments at binding level -- this is a feature that  I would really like to see in Axis2 1.4 release. It allows the user to add <wsp:PolicyAttachment> element in the services.xml and specify policies that applicable bindings. This very useful since it provides a way for the service authors to specify policies for specific bindings. (Some polices are only meaningful at binding level (.e.g security) and at the moment this can be done only by including a WSDL in service archive file)
> NOTE: 
> 1) There are one test failure in JAXWS Integration , and three failures in the integration modules. I will fix them and submit another patch ASAP

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


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


[jira] Updated: (AXIS2-3677) Suggested fixes for 1.4 RC3

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

Sanka Samaranayake updated AXIS2-3677:
--------------------------------------

    Attachment: axis2-3675_and_3677.patch

Uploaded with grant license to ASF

> Suggested fixes for 1.4 RC3
> ---------------------------
>
>                 Key: AXIS2-3677
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3677
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Sanka Samaranayake
>            Assignee: Sanka Samaranayake
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: axis2-3675_and_3677.patch, axis2-3675_and_3677.patch, suggested-changes-rc2.patch
>
>
> I really like to include the attached patch in rc3 which contains following fixes
> a) Binding Message Level Dispatching -- a minor fix which set the target Axis binding message in the message context.
> b) Minor fix which set policies in the appropriate element of the generated WSDL based on the Axis Service and Axis Service Binding hierarchy.
> c) Support for policy attachments at binding level -- this is a feature that  I would really like to see in Axis2 1.4 release. It allows the user to add <wsp:PolicyAttachment> element in the services.xml and specify policies that applicable bindings. This very useful since it provides a way for the service authors to specify policies for specific bindings. (Some polices are only meaningful at binding level (.e.g security) and at the moment this can be done only by including a WSDL in service archive file)
> NOTE: 
> 1) There are one test failure in JAXWS Integration , and three failures in the integration modules. I will fix them and submit another patch ASAP

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


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


[jira] Resolved: (AXIS2-3677) Suggested fixes for 1.4 RC3

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

Davanum Srinivas resolved AXIS2-3677.
-------------------------------------

    Resolution: Fixed

Fixed in svn revision 643008

> Suggested fixes for 1.4 RC3
> ---------------------------
>
>                 Key: AXIS2-3677
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3677
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Sanka Samaranayake
>            Assignee: Sanka Samaranayake
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: axis2-3675_and_3677.patch, axis2-3675_and_3677.patch, suggested-changes-rc2.patch
>
>
> I really like to include the attached patch in rc3 which contains following fixes
> a) Binding Message Level Dispatching -- a minor fix which set the target Axis binding message in the message context.
> b) Minor fix which set policies in the appropriate element of the generated WSDL based on the Axis Service and Axis Service Binding hierarchy.
> c) Support for policy attachments at binding level -- this is a feature that  I would really like to see in Axis2 1.4 release. It allows the user to add <wsp:PolicyAttachment> element in the services.xml and specify policies that applicable bindings. This very useful since it provides a way for the service authors to specify policies for specific bindings. (Some polices are only meaningful at binding level (.e.g security) and at the moment this can be done only by including a WSDL in service archive file)
> NOTE: 
> 1) There are one test failure in JAXWS Integration , and three failures in the integration modules. I will fix them and submit another patch ASAP

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


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


[jira] Updated: (AXIS2-3677) Suggested fixes for 1.4 RC3

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

Sanka Samaranayake updated AXIS2-3677:
--------------------------------------

    Attachment: axis2-3675_and_3677.patch

Dims, 

The above patch contains the suggested fixes for AXIS2-3685 and AXIS2-3677 which I propose for axis2-1.4 release. Pls note that it excludes changes that I've made to EndpointReferenceHelper which Brian. 

Thanks,
Sanka



> Suggested fixes for 1.4 RC3
> ---------------------------
>
>                 Key: AXIS2-3677
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3677
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Sanka Samaranayake
>            Assignee: Sanka Samaranayake
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: axis2-3675_and_3677.patch, suggested-changes-rc2.patch
>
>
> I really like to include the attached patch in rc3 which contains following fixes
> a) Binding Message Level Dispatching -- a minor fix which set the target Axis binding message in the message context.
> b) Minor fix which set policies in the appropriate element of the generated WSDL based on the Axis Service and Axis Service Binding hierarchy.
> c) Support for policy attachments at binding level -- this is a feature that  I would really like to see in Axis2 1.4 release. It allows the user to add <wsp:PolicyAttachment> element in the services.xml and specify policies that applicable bindings. This very useful since it provides a way for the service authors to specify policies for specific bindings. (Some polices are only meaningful at binding level (.e.g security) and at the moment this can be done only by including a WSDL in service archive file)
> NOTE: 
> 1) There are one test failure in JAXWS Integration , and three failures in the integration modules. I will fix them and submit another patch ASAP

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


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