> I have another question, can we design an application service with
> Camel to have a mini state managed workflow. For example, we receive an
> webservice request from consumer which needs to be asynchronously
> processed. The asynchronous processing can involve invocation of
> multiple webservices and provide a final update to the consumer.
I have problems with "asynchronous webservice".
Do you want to split your ws-call in call-ws and get-response (two different
webservices)?
Here I would think something like this
from( call-ws-endoint )
.multicast()
.to("jms:processCall")
.to( synchronous-answer-of-ws-call ) // 'your call was recieved'
;
from("jms:processCall)
// do you other ws-calls
.to("jdbc:write-answer-to-database")
from( get-result-ws-call )
// look into db for returning the result
Jan
>
> I looked into the AsyncProcessor of Camel and as this AsynProcessor of
> Camel is not using persistence store I am a bit reluctant to use it and
> have some sort of persistent store involved so that in case there is a
> Error then I will be able to process the request from where it failed.
>
> Do you think Camel is a good framework for this kind of use cases.
>
> Thanks & Regards,
> Subbu.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Best-
> Practice-to-write-Processor-tp5756514p5757163.html
> Sent from the Camel Development mailing list archive at Nabble.com.
