Return-Path: 
 <users-return-14837-apmail-cxf-users-archive=cxf.apache.org@cxf.apache.org>
Delivered-To: apmail-cxf-users-archive@www.apache.org
Received: (qmail 1375 invoked from network); 5 May 2009 03:43:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 5 May 2009 03:43:12 -0000
Received: (qmail 19687 invoked by uid 500); 5 May 2009 03:43:12 -0000
Delivered-To: apmail-cxf-users-archive@cxf.apache.org
Received: (qmail 19575 invoked by uid 500); 5 May 2009 03:43:11 -0000
Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@cxf.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@cxf.apache.org>
List-Post: <mailto:users@cxf.apache.org>
List-Id: <users.cxf.apache.org>
Reply-To: users@cxf.apache.org
Delivered-To: mailing list users@cxf.apache.org
Received: (qmail 19565 invoked by uid 99); 5 May 2009 03:43:10 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2009 03:43:10 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2009 03:43:01 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1M1BYG-00045B-NU
	for users@cxf.apache.org; Mon, 04 May 2009 20:42:40 -0700
Message-ID: <23380510.post@talk.nabble.com>
Date: Mon, 4 May 2009 20:42:40 -0700 (PDT)
From: Glen Mazza <glen.mazza@gmail.com>
To: users@cxf.apache.org
Subject: Re: soap:body content is base64 encoded - is that expected?
In-Reply-To: <23369457.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: glen.mazza@gmail.com
References: <23369457.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


I think it depends on what the WSDL says the input message type should be. 
For example, look at the WSDL fragment at the "For Step #4, replace..."
section here:  http://www.jroller.com/gmazza/entry/using_mtom_and_apache_fop

Glen


Nick Cotter wrote:
> 
> Hi,
> 
> Should soap:body content be sent base64 encoded by default?
> 
> I've been wiring up a web service client with CXF in Mule, in order to
> send some quite ordinary XML:
> 
> <HS_CreatePersonRequest>
> 	<forenames>Frank</forenames>
> 	<initials>S</initials>
> 	<surname>Spencer</surname>
>         ...etc
> </HS_CreatePersonRequest>
> 
> - no images or raw binary data of any kind - and I'm seeing something
> unexpected in the soap content I'm sending, namely that the body content
> is base64 encoded:
> 
> <soap:Body>
> 		<HS_CreatePersonRequest
> 		
> xmlns="http://www.capita-software.co.uk/ABC/services/WSHsgCreatePerson/"
> 			xmlns:ns3="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> 			xsi:type="ns3:base64Binary">
> PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48SFNfQ3JlYXRlUGVyc29uUmVxdWVzdD48Zm9yZetc....
> etc...
> 		</HS_CreatePersonRequest>
> 	</soap:Body>
> 
> I thought I'd see the XML in there, but I don't - the base64 code contains
> the XML I'm expecting, so maybe this is ok. Is it?
> 
> Kind regards
> 
> Nick
> 

-- 
View this message in context: http://www.nabble.com/soap%3Abody-content-is-base64-encoded---is-that-expected--tp23369457p23380510.html
Sent from the cxf-user mailing list archive at Nabble.com.