On Mon, Aug 20, 2012 at 10:15 PM, ceposta <[email protected]> wrote:
> suppose i could have asked this before i started… but i'm almost done with a
> dzone refcard for most-used camel components and their configs. I wanted to
> limit it to 6 components, and I chose:
>
> JMS/ActiveMQ
> CXF
> HTTP4/Jetty
> Direct/Seda
> Mock/Test
>
> Any comments? Are there any glaring ones that should have been considered
> ahead of those 6?
>

Yes the file/ftp components are very often used.
And of course the bean component is very often used as well.

I strongly suggest to add at least file as its very easy to get
started with using. Everybody knows how to create a file and copy it
to a directory, etc. Where as invoking a SOAP webservice is hazzle
with a wsdl and tool such as soapui to do it.

And the Test component is very rarely used. Often for testing purpose
the Mock is sufficient.
And some people use the JPA, SQL, JDBC or MyBatis for SQL stuff.
And then we got the log component as well. Maybe mention it too.
And the socket based such as mina/netty is also used a fair bit as well.
And some uses the validation/xslt for XML stuff.


File / FTP
Log
Bean
Direct/Seda
Mock
JMS/ActiveMQ
HTTP4/Jetty
CXF

And you maybe need some REST as well.
CXF-RS / Restlet


HTTP4 library is not so easy to configure as the old HTTP client 3.x was.
There is an alternative AHC which is a great http framework (it has
support for other stuff as well, REST / websocket / webdav etc.)



>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Dzone-Refcard-tp5717729.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
FuseSource
Email: [email protected]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Reply via email to