[ 
https://issues.apache.org/jira/browse/AXIS2-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rich Scheuerle reassigned AXIS2-2146:
-------------------------------------

    Assignee: Rich Scheuerle

> server does not check for SOAP12 message sent to SOAP11 endpoint
> ----------------------------------------------------------------
>
>                 Key: AXIS2-2146
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2146
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Mike Rheinheimer
>         Assigned To: Rich Scheuerle
>         Attachments: patch.txt, patch_20070209.txt
>
>
> The SOAP1.2 spec has instructions of what to do when a SOAP message does not 
> match the SOAP version of the endpoint:
> http://www.w3.org/TR/soap12-part1/#version
> Currently, the JAXWS runtime does not check incoming SOAP message versions 
> against the SOAP version of the endpoint.  This patch fixes this.  It is a 
> non-trivial patch due to several problems:
> 1.  First, the server was ignoring the incoming message soap version.  This 
> was remedied first.
> 2.  (1) resulted in discovering that the Builder in the transport layer on 
> the client was being configured according to the outbound request SOAP 
> namespace.  This resulted in the Builder throwing an exception due to the 
> incoming response message SOAP version not matching with the configured 
> version on the Builder.
> 3.  Several unit tests needed fixin.  Some of them were sending SOAP12 
> messages to SOAP11 endpoints.  This is not supported, but worked in our 
> environment because we ignored the SOAP versions, and the messages carried no 
> SOAP protocol specific information that would cause a break.
> This has resulted in yet another issue that I will address in another patch.  
> The client side is also not checking soap versions on incoming requests.  
> I'll fix this very soon.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to