Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <446690352.1125675972548.JavaMail.jira@ajax.apache.org>
Date: Fri, 2 Sep 2005 17:46:12 +0200 (CEST)
From: "Eran Chinthaka (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-198) Extracting Char Encoding and version
 information from incoming SOAP messages
In-Reply-To: <1551317406.1125653952026.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/AXIS2-198?page=all ]
     
Eran Chinthaka resolved AXIS2-198:
----------------------------------

    Fix Version: 0.92
     Resolution: Fixed

Fixed those information to be read even in StAXOMBuilder. 

> Extracting Char Encoding and version information from incoming SOAP messages
> ----------------------------------------------------------------------------
>
>          Key: AXIS2-198
>          URL: http://issues.apache.org/jira/browse/AXIS2-198
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: core, om, transports
>     Versions: 0.91
>     Reporter: Eran Chinthaka
>     Assignee: Eran Chinthaka
>     Priority: Minor
>      Fix For: 0.92

>
> Current StAXSOAPModel builder do not get char set encoding and version from the recd SOAP message. This has to be fixed and there should be a check to see whether transport charset information and SOAP message information do tally.
> Current OMOutput overrides the char information in the SOAP Document.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira