Return-Path: 
 <issues-return-4159-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 817409562
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Mon, 11 Jun 2012 21:11:43 +0000 (UTC)
Received: (qmail 10296 invoked by uid 500); 11 Jun 2012 21:11:43 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 10272 invoked by uid 500); 11 Jun 2012 21:11:43 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 10264 invoked by uid 99); 11 Jun 2012 21:11:43 -0000
Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2012 21:11:43 +0000
Received: from isssues-vm.apache.org (localhost [127.0.0.1])
	by issues-vm (Postfix) with ESMTP id 2482314002F
	for <issues@camel.apache.org>; Mon, 11 Jun 2012 21:11:43 +0000 (UTC)
Date: Mon, 11 Jun 2012 21:11:42 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <184882655.4270.1339449103152.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <208773999.9846.1335806149324.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-5234) Spring-WS does neither set message
 body nor message headers if exchange is not outCapable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CAMEL-5234?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1329=
3086#comment-13293086 ]=20

Christian M=C3=BCller commented on CAMEL-5234:
-----------------------------------------

Looks good for me too.
               =20
> Spring-WS does neither set message body nor message headers if exchange i=
s not outCapable
> -------------------------------------------------------------------------=
----------------
>
>                 Key: CAMEL-5234
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5234
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring-ws
>    Affects Versions: 2.7.5, 2.8.4, 2.9.2
>            Reporter: Benjamin Gniza
>            Assignee: Babak Vahdat
>              Labels: in, out, out-capable, response, spring-ws
>             Fix For: 2.9.3, 2.10.0
>
>         Attachments: CAMEL-5234.patch
>
>
> Spring-WS component does not behave as expected from pipes and filters pa=
ttern if exchange is not _outCapable_.
> If _ExchangeHelper_._isOutCapable_ returns false for the given _exchange_=
 the IN-message is returned instead of the WS-Response.
> Example:
> {code:title=3DExampleRoute}
>         from("timer://foo?fixedRate=3Dtrue&period=3D1000")//
>                 .setBody().simple("<ex:getExampleResponse xmlns:ex=3D\"ht=
tp://example.com/\">" //
>                         + "       <id>1</id>" //
>                         + "     </ex:getExampleResponse>")//
>                 .to("spring-ws:http://localhost:9000/Example")//
>                 .to("file://responses");
> {code}
> In the example above I would expect the WS-response written to the files =
in the responses directory. Currently (since 2.7.3) the IN message is writt=
en to the files.
> This is caused by _SpringWebserviceProducer#process_ because it only sets=
 headers and body for the OUT-message if _isOutCapable_ is _true_.
> Workaround (maybe this has side effects!):
> {code:title=3DExampleRoute}
>                 from("timer://foo?fixedRate=3Dtrue&period=3D1000")//
>                 .setExchangePattern(ExchangePattern.InOut) // <-- Overrid=
e with InOut Pattern
>                 .setBody().simple("<ex:getExampleResponse xmlns:ex=3D\"ht=
tp://example.com/\">" //
>                         + "       <id>1</id>" //
>                         + "     </ex:getExampleResponse>")//
>                 .to("spring-ws:http://localhost:9000/Example")//
>                 .to("file://responses");
> {code}
> This behavior has been implemented to fix CAMEL-3974. From my point of vi=
ew its counter intuitive since other processing-steps don't check the excha=
nge's _outCapability_.
> It took me several hours to find out why I always got the IN message back=
, although the webservice was called correctly and returned correct results=
.
> Maybe an option should be provided to control this behavior. At least a l=
og-message should be written to explain, that the webservice-reponse is thr=
own away.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira