Hi
1)
I can only think of the error handler stuff we have in java DSL. In Spring you
should use the errorHandler attribute and define it as plain spring beans.
2)
And I think we have a minor "name not the same" issue:
- Java DSL: exception(MyBusinesssException.class).to("xxx");
- Spring DSL: <onException>
Maybe we should try to get the 2 names as the same?
onException sounds as the best suited DSL name to me.
3)
I am sure there are others we have missed.
4)
I would love that we improve the <package> or to allow setting 1..N classes
instead or ref to spring ids. The <package> is sometimes a bit to "magic" for
new users. Something to consider for Camel 2.0
Also when doing unit testing it would be great to be sure only YOU route is
loaded and not all in the same package.
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Jon Anstey [mailto:[EMAIL PROTECTED]
Sent: 25. september 2008 22:44
To: [email protected]
Subject: [SPAM] Spring vs. Java DSL
Hi all,
Figured I'd ask before going any deeper into this :) If any one knows off
hand a piece of Java DSL that isn't available in the Spring DSL, please add
a comment in CAMEL-745. I'd really like to get any important bits in before
the 1.5 release.
I'm going to do more comparison of the two tomorrow.
--
Cheers,
Jon
http://janstey.blogspot.com/
