Hi, Random thinks, comments very welcome °°°°° The **pipeline** concept
You have a content You have an "easy to build" pipeline with different good job components You put your content into the pipeline, and you have your lovely output. Put a non-digest xml and get a graphical templated pdf (for example). GREAT ! Really ! you can easily PROCESS your content. BUT, This image draws the limits or the pipe : Your content is gasoline. At the oil plateform, throw in the pipe, run the pipe, and get out on coast, with no way to escape or take another route. (humm, well, I hope so ;) ). So, when you process your content with the pipe concept, there is no way to escape if something goes wrong (or well) in your content, if your content have full fill some criterias,... Also, it's not so easy to duplicate an input and do some "parallel" processing, split can be a pita, loop too, ... °°°°° The **routes** concept In this concept, a route is an aggregation of Entreprise Integration Pattern (EIP) than can allow the content to drive his car. Processing line is not still piped, but rich, variable, dynamically selected. Apache Camel provide an implementation of this EIP, overview here : http://camel.apache.org/enterprise-integration-patterns.html BUT, It's for now just an idea, a point of interest, no hands in, but a great opportunity I think. °°°°° Last (but not least ?) The Camel framework also provide an amazing number of connectivity tools, that can allow to retrieve and publish document in all situations. Lenya as a 4x4 wheels ! :) Find list here : http://camel.apache.org/transport.html °°°°°° NB : this is the "foundation" document of EIP : http://www.enterpriseintegrationpatterns.com/toc.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org For additional commands, e-mail: dev-h...@lenya.apache.org
