Return-Path: 
 <users-return-51447-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 58BFA178AE
	for <apmail-camel-users-archive@www.apache.org>;
 Fri, 10 Oct 2014 17:17:20 +0000 (UTC)
Received: (qmail 39291 invoked by uid 500); 10 Oct 2014 17:17:19 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 39246 invoked by uid 500); 10 Oct 2014 17:17:19 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 39229 invoked by uid 99); 10 Oct 2014 17:17:19 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 17:17:19 +0000
X-ASF-Spam-Status: No, hits=2.8 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ch007m@gmail.com designates
 209.85.217.174 as permitted sender)
Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com)
 (209.85.217.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 17:16:53 +0000
Received: by mail-lb0-f174.google.com with SMTP id p9so3543448lbv.33
        for <users@camel.apache.org>; Fri, 10 Oct 2014 10:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=+/JzxOjBFBJTdyqogSQCCLrPIBHOEvqKaKrIxaALUm0=;
        b=nhGliB82br4HPGI9jBGUTyF03GJ+oecRvrMwWyMbC54qkRXTSqCXLKH6kPAZ35m8mN
         9o/ljghAiIYZg4uGFDNDlKo1cT1tfH/ivUxcYsAf3tc/sF1+JyP05+myn1s7BeLMUELi
         McEFW6xY7bBzuy4JSo2+whSvgJyoRYQZAKM+mrawjNDsftAbul7Yb5KWc3zfB08+bPof
         L57fbKh0YDH8pNdOklYXjIQhL11koEw3wOEbesKKv6TKMNngFJZe+0zp74haM0LRgA2d
         fszTzBU80ZzWiX4Jd0URZrBgQ7rxqZhfTNB44IyrKnNSeiS55uMNlUKgd2HKH48E8J0v
         KWiQ==
MIME-Version: 1.0
X-Received: by 10.112.73.4 with SMTP id h4mr6109185lbv.19.1412961413032; Fri,
 10 Oct 2014 10:16:53 -0700 (PDT)
Received: by 10.25.212.137 with HTTP; Fri, 10 Oct 2014 10:16:52 -0700 (PDT)
In-Reply-To: <1412939176116-5757474.post@n5.nabble.com>
References: <1412862242676-5757448.post@n5.nabble.com>
	<CAAxZHdd1iknTJjG9=oUX_eqnBThh1_ki-CviQdQgKsF-FNLqCw@mail.gmail.com>
	<1412926122913-5757462.post@n5.nabble.com>
	<1412939176116-5757474.post@n5.nabble.com>
Date: Fri, 10 Oct 2014 19:16:52 +0200
Message-ID: 
 <CAAxZHddK833tOw1+DZjABioT-yUOM=phPVpdtDrYiPqbX16NuQ@mail.gmail.com>
Subject: Re: Http bridgeEndpoint to proxy a distant server
From: Charles Moulliard <ch007m@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=001a11c264401af2a7050514b7ae
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c264401af2a7050514b7ae
Content-Type: text/plain; charset=UTF-8

Hi Antoine,

Add a beanProcessor (where in the code you can put a breakpoint) after the
HTTP endpoint calling your service and before the transform so you will be
able to check the objects present in the exchange.

Regards,


On Fri, Oct 10, 2014 at 1:06 PM, antb59 <antb59@gmail.com> wrote:

> Hello,
>
> After checks, it seems that the trace you mentionned is not an error.
>
> If I do a simple proxy just like in this example :
>
> http://camel.apache.org/how-to-use-camel-as-a-http-proxy-between-a-client-and-server.html
>
>         <route id="Identification">
>                 <from uri="restlet:/identification?restletMethod=POST" />
>                 <to uri="
> http://localhost:8012/identification.xml?bridgeEndpoint=true" />
>         </route>
>
> The trace you mentionned is present in DEBUG. In this case the http request
> is correctly processed and the restlet returns the result to the user.
>
>
> The fact is I don't manage to manipulate the distant server response.
>
> The following configuration works :
>
>         <route id="Identification">
>                 <from uri="restlet:/identification?restletMethod=POST" />
>                 <to uri="
> http://localhost:8012/identification.xml?bridgeEndpoint=true" />
>                 <convertBodyTo type="java.lang.String"/>
>         </route>
>
> => return of restlet :
> <?xml version="1.0" encoding="iso-8859-1"?><identificationResponse
> status="0" />
>
> The following configuration doesn't work :
>
>         <route id="Identification">
>                 <from uri="restlet:/identification?restletMethod=POST" />
>                 <to uri="
> http://localhost:8012/identification.xml?bridgeEndpoint=true" />
>                 <convertBodyTo type="java.lang.String"/>
>                 <marshal ref="xmljson" />
>         </route>
>
> => No return from restlet, the response is hanging until timeout
>
> With the following route, the result seems to be truncated :
>
>         <route id="Identification">
>                 <from uri="restlet:/identification?restletMethod=POST" />
>                 <to uri="
> http://localhost:8012/identification.xml?bridgeEndpoint=true" />
>                 <transform>
>                         <simple>Test : ${bodyAs(String)}</simple>
>                 </transform>
>         </route>
>
> => Return from the restlet :
> Test : <?xml version="1.0" encoding="iso-8859-1"?><identificationResponse
> statu
>
> The end of the response seems to be truncated.
>
> Maybe my problem is linked to InputStream return by the distant server ?
> How can I solve this using only DSL ?
>
> Regards,
> Antoine.
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Http-bridgeEndpoint-to-proxy-a-distant-server-tp5757448p5757474.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

--001a11c264401af2a7050514b7ae--