Hi Claus, thanks for help.
The greatest pattern for me now is the Routing Slip one, because it could
act like a pipeline for exec: commands endpoints, as we used do with bash
command.
Buy what I can not still figure out is how to pass information from the rest
request from my ControllerService to my ControllerBean.
I think this is important, because in this way, the ControllerBean could use
it to set the list of the exec endpoints that should receive the Exchange.
If I am corret with my thoughts, my very first issue now is get information
from the request and put it in the camel context for ControllerBean access
it.
So I try this:
@Path("/")
public class ControllerService {
@GET
@Path("/start")
@Produces("text/plain")
public String startRoute(*@QueryParam("commands")* String *commands*)
throws Exception {
//here, I do not want to deal with this "hiphen delimeted" *commands*
string receive from the request
//I think this method is not for processing the request but just for a
acces pont for my batch executable commands
//But I hope to achieve a way to pass this string to my ControllerBean
//because ControllerBean will use this string to create the list of
endpoints the will receive the messages
//and set it as a header for Routing Slipe implementation
//I wandering if I return the *commands* string here, the
ControllerBean
would can get from camelContext....
return commands;
}
I know that there are another changes to do for the Routing Slip pattern
implementation, but, for now, I would like to test my concepts by small
steps.
Am I in the correct way?
All best wishes for the team!!! and many thanks!!!
--
View this message in context:
http://servicemix.396122.n5.nabble.com/how-to-intall-servicemix-exec-in-apache-servicemix-4-4-1-fuse-07-11-tp5714116p5714222.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
