axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikhil Thaker (JIRA)" <>
Subject [jira] Reopened: (AXIS2-4126) Remove SOAP Version Restriction from JAX-WS Provider Endpoint
Date Tue, 11 Nov 2008 14:54:44 GMT


Nikhil Thaker reopened AXIS2-4126:

The new StringProviderTests failed due to incorrect port associated in the endpoint URL. I
will correct the problem and commit the test case.

> Remove SOAP Version Restriction from JAX-WS Provider Endpoint
> -------------------------------------------------------------
>                 Key: AXIS2-4126
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: jaxws
>            Reporter: Nikhil Thaker
>            Assignee: Nikhil Thaker
>         Attachments: apache_svn_patch.txt
> This JIRA is for removing SOAP Version Restriction from Provider Endpoints. Currently
a JAX-WS Provider Endpoint can support a SOAP11 or SOAP 12 call based on the soap version
defined in the binding type annotation. With this JIRA I am introducing a new constant that
SOAP_HTTP_BINDING can be used in @BindingType annotation, when this new constant is used 
the java endpoints will cater to SOAP11 and SOAP12 messages.
> This JIRA will also add proper validation checks to support the new constant, for example
it will ensure that a SOAP Fault will be thrown when a response of soap12 is sent on a soap11
request etc. This JIRA also adds code to update various validation checks for new constant
during web services deployment.
> This JIRA also adds test cases in JAXWS-Integration module to test various scenarios
for this new constants and validations.

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:
For additional commands, e-mail:

View raw message