----- Original Message -----
From: Mark Hapner <[EMAIL PROTECTED]>
> A major objective of EJB is to achieve the creation of a multi-user
service by
> implementing single threaded components.
So EJB was never intended to handle parallel workflow, as occurs commonly in
large business systems? Then what good is a session bean?
> EJB 2.0 will significantly expand the EJB app domain by adding support
> for asynchronous invocation (JMS integration).
Which is only half of the problem. EJB will not be complete until it also
specifies how to "create" threads within user beans in such a way that the
container still has a handle on them. This is a very simple problem.
> So, the question is not what you can do within your container it is what
your
> container can do for you :>). Why should you be worrying about creating
threads if
> you can get the container to handle all of that complexity?
Because no container on the market will currently let me do parallel
asynchronous workflow while still being strictly EJB 1.1 compliant. That
says more about the specification than the container to me.
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".
