Really, using a thread for something like that is perfect. Since are not
really changing the normal request/response symantics, a thread is fine.
That said, I'd recommend looking at a thread pool of some sort to keep some
sort of limit on how much extra stuff is happening.
Dan
On Wednesday 28 July 2010 10:48:56 pm ironman77 wrote:
> Hi All,
>
> In a cxf based webservice if I want do some separate ("parallel")
> processing depending on request data without effecting the existing flow,
> is threading the only option?
>
> For example, consider the following scenario:
>
> Existing cxf service: Request --->BusinessLogic-->Response
>
> New cxf service: Request--->BusinessLogic-->Response
>
>
> --->DoSomething else
>
> In the new cxf service, everthing remains same from request-response
> perspective, I want to do some other logic. What is the best way to design
> such scenario?
>
> Thank you,
> J
--
Daniel Kulp
[email protected]
http://dankulp.com/blog
