Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.gr;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
  b=pQMoBh/NIR0grCvuz05XUTFTwCoOkYonvdcW01oGGSQtfKtGjizM/PVZaCeNMnzG6mJzvWZllW8UW715Zaia8u94ZWpiX6tMRUdN2M+Zva/FPeBBeeneYx7k0wKwoLN2agGNqdIN4Oo9R7GNpqX+AlSbxVIE30pPE9AMoqC0ctc=
  ;
Message-ID: <4B2A0123.4050404@yahoo.gr>
Date: Thu, 17 Dec 2009 12:00:03 +0200
From: Alexandros Karypidis <akarypid@yahoo.gr>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Newbie: convert XML Source object to a String in an "as-is" manner
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I use conversion from an XML "Source" object to a "String" at some point 
in my route. The default conversion seems adds a new-line character 
after each element. This breaks my integration because in my case, the 
message is a SOAP envelope with WS-Security headers regarding a signed 
element.

Is there a way to get around this? All I need is for the XML to become a 
"String" in an "as-is" manner (with no formatting). My current (Spring) 
configuration is:

    ...
    xmlns:camel-cfg="http://camel.apache.org/schema/spring"
    xmlns:camel-cxf="http://camel.apache.org/schema/cxf"
    ...
    <camel-cfg:camelContext id="camelContext" trace="true" >
        <camel-cfg:route>
            <camel-cfg:from uri="cxf:bean:myWebServiceProvider" />
            <camel-cfg:convertBodyTo type="java.lang.String" />
            <camel-cfg:to uri="jms:queue:weblogic/my-Queue-0" />
            <camel-cfg:to uri="file:///fileEavesdropMSG-IN/" />
        </camel-cfg:route>
    </camel-cfg:camelContext>

If I don't convert to String, the message doesn't get into the JMS 
queue. If  I do, the message's signature breaks...

Thanks in advance,
Alex

P.S. If it matters, the provider class (which uses Provider<Source>) 
looks like this:

@WebServiceProvider(targetNamespace = "...", serviceName = "...", 
portName = "...", wsdlLocation = "...")
@ServiceMode(Mode.MESSAGE)
@BindingType(value = HTTPBinding.HTTP_BINDING)
public class MyMessagingServiceProvider implements Provider<Source> {
...