|
That
works, but it's synchronous. You may want to use a MessageDrivenBean instead,
for asynchronous execution. Collecting result information from asynchronous
execution could be troublesome, so you should think about it carefully(or
explain the case better).
HTH,
Juan Pablo Lorandi
Chief Software
Architect
Code Foundry Ltd.
Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com Disclaimer:
Opinions expressed are entirely
personal and bear no relevance to opinions held by my employer.
Code Foundry Ltd.'s opinion is that I
should get back to work.
|
Title: Message
- Calling a bean from another bean independent of each ot... deepak
- Re: Calling a bean from another bean independent o... CharanKumar
- Juan Pablo Lorandi
