Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
From: =?iso-8859-1?Q?Jan_Mat=E8rne_=28jhm=29?= <apache@materne.de>
To: <users@camel.apache.org>
References: <1470934315836-5786330.post@n5.nabble.com>
In-Reply-To: <1470934315836-5786330.post@n5.nabble.com>
Subject: AW: Any issues having Camel Processor doing all the Works
Date: Fri, 12 Aug 2016 14:59:46 +0200
Message-ID: <001c01d1f499$67b14720$3713d560$@de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AdH0ec0eR3Kkwlm3SV+J5AEkGw2aPAAHnlfw
Content-Language: de
archived-at: Fri, 12 Aug 2016 13:00:03 -0000

Of course you could do all in plain Java.
Using Camel introduces a lot of dependencies and you have to think about =
its
benefits and drawbacks (as by each architectural decision).

What you earn (IMO):
- code is easier to read
- easier asynchronous behaviour
- easier integration with other technologies

And of course, learning new things requires time.
You have to decide if it's worth (for you/your project).


Jan


> -----Urspr=FCngliche Nachricht-----
> Von: JamesG [mailto:ehchn1@hotmail.com]
> Gesendet: Donnerstag, 11. August 2016 18:52
> An: users@camel.apache.org
> Betreff: Any issues having Camel Processor doing all the Works
>=20
> Hi,
>=20
> Instead of doing the routing using DSL, web service calling with CXF
> component, enriching, intercepting, etc , why not just have a =
Processor
> and put all the java codes there? For a Camel beginner, this seems
> pretty much easier to get the things done (definitely for those with
> java background), but I am not sure how effective or correct this
> approach is.
>=20
> Below is a sample scenario:
> 1)  Call a web service to retrieve some result.
> 2)  Based on the result, decide whether to proceed calling another
> service.
>=20
> If I would to achieve the above through Processor, it's merely few
> lines of codes.
> But if I'm using DSL to do it, the work is going to be more (cxf
> endpoint, enrich, when, simple).
>=20
> Appreciate any advises and comments.
>=20
>=20
> Thanks in advance.
>=20
>=20
>=20
>=20
> --
> View this message in context: http://camel.465427.n5.nabble.com/Any-
> issues-having-Camel-Processor-doing-all-the-Works-tp5786330.html
> Sent from the Camel - Users mailing list archive at Nabble.com.