Mark,
So far the discussion has been about the useability of thread support,
and no one contradicted their usability. I'm not sure JMS is sufficient
for what developers have in mind, and connectors would be an overkill
for many applications.
It's clear that EJB 1.1 should not support threads, nor the applications
should attempt to use them.
But what about adding that support to a future version of EJB?
If enough people request it, you will see it being supported by the
major vendors, which unless properly specified, will break the WORA
promise of EJB.
arkin
MARK HAPNER wrote:
>
> The threading restrictions, JNI restrictions, etc. that EJB 1.1 imposes
> define are an important part of the EJB Component/Container contract on
> which EJB portability is based.
>
> Some EJB vendors may provide access to Java features that go beyond the
> minimum set of Java permissions defined by EJB 1.1 and J2EE specs;
> however, no EJB vendor is required to support EJBs that require more
> than the specified minimum permissions.
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
