JMS is a resource manager. It can create a new thread, open sockets,
read to files, etc. Just like a JDBC driver or the EJB container itself.
As a general rule:
* The container is responsible for managing the life cycle of the
application, threads, security, transaction, etc
* The application is the business logic and is limited to doing just
that.
* Your application interacts with services through resource manager and
connector APIs. These services (which are not your application) can open
threads, read to file, etc.
The only problem of EJB 1.1 is that it does not specify how to hook
these connectors into the server, so you cannot (at the moment) add your
own services.
arkin
> I don't understand. Surely invoking JMS in any fashion results in a new thread
> being created. Is this thread creation "legal" because it is the container
> vendor who has implemented it?
>
> > This assumes the container actually implements JMS of course.
> > Again, maybe someday we'll have some standard facilities for creating
> > and managing container-compatible threads, but not yet.
>
> The more I work with this specification, the more I dislike it.
>
> Thanks for your informative and thoughtful reply.
>
> Cheers,
> Laird
>
> ===========================================================================
> 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".
