Ok, so where in the code for an SE is the main processing loop? Is this a method I can override? I just need somewhere to be able to create a loop that starts trying to call my dequeue logic, and then send dequeued data out to an http provider.
gnodet wrote: > > The JBI spec defines the lifecycle of SA / SE. > If by "starting the SE" you mean "activating the JBI endpoint", > it should be done when the SA is started. Btw, the SE has to be started > before the SA is deployed, else the deployment will fail. > > On 5/10/07, Benamin <[EMAIL PROTECTED]> wrote: >> >> >> I am having problems trying to figure out how to make an SE startup >> automatically. I have an SE that I want to have retrieve data from a >> queue. >> Once dequeued, the SE should be able to send this data to an >> HTTP-Provider >> and continue trying to dequeue more data. I've looked into putting this >> loop into the processInOut method for the MyEndpoint class of the SE, and >> then just send the dequeued data in the out parameter. Is this the right >> way to go? >> >> Also, how do I configure this SE to start as soon as my SA is deployed? >> -- >> View this message in context: >> http://www.nabble.com/Starting-an-SE-tf3723654s12049.html#a10419975 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Principal Engineer, IONA > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Starting-an-SE-tf3723654s12049.html#a10420834 Sent from the ServiceMix - User mailing list archive at Nabble.com.
