The reason you're not allowed to do threading in EJB is that it is the
containers responsibility to handle those. So the basic answer to your
question, how people handle threads, is: they don't.
/Marcus Ahnve
Sun Java Center
Sweden
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew T. Machczynski
> Sent: Tuesday, February 15, 2000 2:57 PM
> To: [EMAIL PROTECTED]
> Subject: EJB: Multi-threading: how to cope with the 1.1 spec?
>
>
> Hey all,
>
> So multithreading isn't really allowed in EJBs according to the
> 1.1 spec? How
> are people
> dealing with this in a netcentric architecture? I could see that
> if you have
> client control
> (thin client), that you could place the multithreading in the client tier.
> Since you don't
> in a browser-based environment, are most people controlling the
> multithreading
> from an access bean perspective? From .jsp?
>
> I'm curious as to what people are generally doing as a "best practice".
>
> Thanks,
>
> Matt Machczynski
> [EMAIL PROTECTED]
>
> ==================================================================
> =========
> 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".
>
>
===========================================================================
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".
