Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 13 May 2016 13:26:12 +0000 (UTC)
From: =?utf-8?Q?J=C3=BCrgen_Kindler_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12969532.1463145938000.184692.1463145972842@Atlassian.JIRA>
In-Reply-To: <JIRA.12969532.1463145938000@Atlassian.JIRA>
References: <JIRA.12969532.1463145938000@Atlassian.JIRA> <JIRA.12969532.1463145938419@arcas>
Subject: [jira] [Created] (CAMEL-9965) Throw meaningful exception of a
 streamed body has been consumed already
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 13 May 2016 13:26:14 -0000

J=C3=BCrgen Kindler created CAMEL-9965:
-------------------------------------

             Summary: Throw meaningful exception of a streamed body has bee=
n consumed already
                 Key: CAMEL-9965
                 URL: https://issues.apache.org/jira/browse/CAMEL-9965
             Project: Camel
          Issue Type: Improvement
          Components: camel-cxf
    Affects Versions: 2.16.3
            Reporter: J=C3=BCrgen Kindler
             Fix For: 2.16.4


As I see in CAMEL-9864 there is an incompatible change about the usage of h=
ttp://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Me=
ssage.html#getBody%28java.lang.Class%29 in case the underlying body is subj=
ect to streaming.

I understand the reasons for that change, but usually Java getters are assu=
med to be not modifying the underlying object.
So it would be nice to add a small hint in the API that indicates that getB=
ody may not be callable multiple times (esp. in context of streams)
In case a stream was already consumed throwing a meaningful exception with =
a hint about how to fix this (either *not* call the method altogether or sw=
itching on stream caching ...) would be great.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)