Hey!
punit malik wrote:
> 2. As we know EJB is targetted towards enterpirse solutions, it will be
> surprising to know if servers hosting these apps. are not multiprocessor. As
> of today, the specs gives container providers the privilege to make use of
> these multiprocessing, but to a bean provider there is a restriction of not
> spawning threads. It maks sense that container would take care of thread
> management etc.
> What if bean provider wants to make use of this multiprocessing by doing a
> background job. For e.g.
> I have a bean that takes customer orders and send it to inventory and sales
> office. This may not be a good example, but my point is there is too much of
> serialization if requests in ejb specs.
> What if like XaResource container has a thread pool that i can submit
> background jobs. This way container willl be able to do thread management
> and bean provider will be able to use multiprocessing.
I believe the EJB-JMS combination is for this kinds of processing.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
