Return-Path: 
 <axis-c-user-return-7209-apmail-ws-axis-c-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org
Received: (qmail 40523 invoked from network); 25 Jul 2009 05:02:47 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 25 Jul 2009 05:02:47 -0000
Received: (qmail 56135 invoked by uid 500); 25 Jul 2009 05:03:52 -0000
Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org
Received: (qmail 56017 invoked by uid 500); 25 Jul 2009 05:03:52 -0000
Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-c-user@ws.apache.org>
List-Id: "Apache AXIS C User List" <axis-c-user.ws.apache.org>
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Delivered-To: mailing list axis-c-user@ws.apache.org
Received: (qmail 55999 invoked by uid 99); 25 Jul 2009 05:03:52 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Jul 2009 05:03:51 +0000
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [209.85.146.178] (HELO wa-out-1112.google.com) (209.85.146.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Jul 2009 05:03:41 +0000
Received: by wa-out-1112.google.com with SMTP id n4so320567wag.0
        for <multiple recipients>; Fri, 24 Jul 2009 22:03:19 -0700 (PDT)
Received: by 10.115.58.9 with SMTP id l9mr5610919wak.3.1248498199435;
        Fri, 24 Jul 2009 22:03:19 -0700 (PDT)
Received: from ?192.168.1.4? ([124.43.160.219])
        by mx.google.com with ESMTPS id f21sm8203322rvb.10.2009.07.24.22.03.15
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Fri, 24 Jul 2009 22:03:18 -0700 (PDT)
Subject: RE: changing the axis2/c message encoding
From: Manjula Peiris <manjula@wso2.com>
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
Cc: Apache AXIS C User List <axis-c-user@ws.apache.org>
In-Reply-To: 
 <9D29FD18CBD74A478CBA86E6EF6DBAD403E9DB89@CHI4EVS04.corp.transunion.com>
References: 
	 <9D29FD18CBD74A478CBA86E6EF6DBAD403E282DC@CHI4EVS04.corp.transunion.com>
	 <9D29FD18CBD74A478CBA86E6EF6DBAD403E9DA11@CHI4EVS04.corp.transunion.com>
	 <9D29FD18CBD74A478CBA86E6EF6DBAD403E9DB67@CHI4EVS04.corp.transunion.com>
	 <9D29FD18CBD74A478CBA86E6EF6DBAD403E9DB89@CHI4EVS04.corp.transunion.com>
Content-Type: text/plain
Date: Sat, 25 Jul 2009 10:33:03 +0530
Message-Id: <1248498183.11261.0.camel@manjula-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

On Thu, 2009-07-23 at 17:35 -0500, Haszlakiewicz, Eric wrote:
> >>>-----Original Message-----
> >>>From: Haszlakiewicz, Eric [mailto:EHASZLA@transunion.com] 
> >>>
> >>>I want to change the character encoding that axis2/c uses to send
> >>>messages to ISO-8859-1.  I am using adb generated code to send and
> >>>receive the requests.  I figured there'd probably be something 
> >>>I can set
> >>>either in the axis2_stub_t service object, or maybe in 
> >>axis2_options_t,
> >>>but I can't find anything that looks appropriate.  
> >>>How do I do this?
> ...snip...
> >The axis2_engine_send function seems to invokes "phases", so 
> >maybe I can
> >hack something in here to set the charset in the msg_ctx?  I found some
> >general documentation about how phases and flows work in axis2, but I'm
> >not quite sure how to go about implementing a phase.  Can someone point
> >me towards an example?  Does this even sound like a reasonable way to
> >get the encoding set?  It seems like it's way harder than it should be.
> 
> well, to response to my own email yet again, I used the addressing
> module from the axis2c sources as an example and managed to create my
> own module that sets the encoding in the msg_ctx and actually sends a
> request with "Content-Type: text/xml;charset=ISO-8851-1" in the headers.
> Unfortunately, the server side still had a problem deserializing the
> request.  I guess this isn't something that has been tested much, and
> I'm probably in for a world of pain to get it working. :(

Did you engage your module in the server sdie ? What are the errors it
sends ?


> 
> eric