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 "Nick Gallardo (JIRA)" <ji...@apache.org> on 2008/01/15 17:12:34 UTC

[jira] Created: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
-------------------------------------------------------------

                 Key: AXIS2-3449
                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
             Project: Axis 2.0 (Axis2)
          Issue Type: New Feature
          Components: jaxws
            Reporter: Nick Gallardo


RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:

1. Update the metadata APIs to expose the RespectBinding data available

2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.

3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  

4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  

5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.



-- 
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-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Nick Gallardo updated AXIS2-3449:
---------------------------------

    Fix Version/s: 1.4

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>             Fix For: 1.4
>
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Nick Gallardo updated AXIS2-3449:
---------------------------------

    Priority: Blocker  (was: Major)

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>            Assignee: Nick Gallardo
>            Priority: Blocker
>             Fix For: 1.4
>
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

David Illsley commented on AXIS2-3449:
--------------------------------------

My understanding was that it is a combination of both...

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nick Gallardo
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Davanum Srinivas commented on AXIS2-3449:
-----------------------------------------

Nick,

Will you be taking this on?

-- dims

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>            Assignee: Nick Gallardo
>             Fix For: 1.4
>
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Nick Gallardo commented on AXIS2-3449:
--------------------------------------

It does look to be a combination of the two.

Can you think of any other wsdl:binding extensions beyond addressing stuff that we would need to be aware of?  

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nick Gallardo
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Brian DePradine commented on AXIS2-3449:
----------------------------------------

Hmm, that's interesting. I thought that the RespectBinding feature was about ensuring that any wsdl:extensions that have wsdl:required="true" have been either understood, or explicitly disabled. I will admit, however, that the requirements are not very clear in this area.

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nick Gallardo
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Davanum Srinivas updated AXIS2-3449:
------------------------------------

    Assignee: Nick Gallardo

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>            Assignee: Nick Gallardo
>             Fix For: 1.4
>
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

David Illsley commented on AXIS2-3449:
--------------------------------------

Hmm, there's WS-Policy, but I'm not sure that's supported in an Axis2/JAX-WS deployment...

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nick Gallardo
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Nick Gallardo commented on AXIS2-3449:
--------------------------------------

Dims,

Yep, I'm going to start on it this week.

-Nick

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>            Assignee: Nick Gallardo
>             Fix For: 1.4
>
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Nick Gallardo updated AXIS2-3449:
---------------------------------

    Affects Version/s: 1.4

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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] Commented: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Brian DePradine commented on AXIS2-3449:
----------------------------------------

I think that it is reasonable to restrict ourselves to the things that are covered by features in JAX-WS 2.1. That leaves WS-Addressing and MTOM. I don't believe that MTOM has any wsdl extensions, but I could be wrong here.

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nick Gallardo
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

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

Nick Gallardo resolved AXIS2-3449.
----------------------------------

    Resolution: Fixed

Fixed in 640319.

> JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature
> -------------------------------------------------------------
>
>                 Key: AXIS2-3449
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3449
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>    Affects Versions: 1.4
>            Reporter: Nick Gallardo
>            Assignee: Nick Gallardo
>            Priority: Blocker
>             Fix For: 1.4
>
>
> RespectBinding is a feature added in JAX-WS 2.1 that allows an endpoint to ignore the binding defined in a wsdl:binding element.  In other words, an endpoint could support both SOAP 1.1 and SOAP 1.2 even though the WSDL may indicate only SOAP 1.1 support for the endpoint.  Here's a quick summary of the work to be done:
> 1. Update the metadata APIs to expose the RespectBinding data available
> 2. Update the annotation processing code in the DescriptionBuilder to process the @RespectBinding annotation.
> 3. Update the WebServiceFeature processing code to account for the RespectBindingFeature.  
> 4. Change the EndpointController to have a toggle point that checks against a RespectBinding property.  
> 5. Update Provider processing code (ProviderDispatcer) to handle the scenario where the return type is invalid according to the input.  This is described in the check that exists in the EndpointController.

-- 
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