Assaf Arkin wrote:
>
> People on this list have come up with usage scenarios where, you have to
> agree, neither EJB 1.1 nor EJB 2.0 + JMS are sufficiently addressing
> their needs.
>
> The issue here is not about redoing thread pooling and thread management
> instead of the container, but being able to get a continueous background
> process to run inside the EJB container.
>
> And if enough people do need it in their production environment, then it
> should be addressed as a WORA issue and become part of the specs.
I second that opinion. We shouldn't have to expose proprietary features to do
service (startup-time) components and thread management. However in the
absense of adequate standards, we are forced to expose proprietary features
to allow customers to do what they need to.
________________________________________________________________________________
Evan Ireland Sybase EA Server Engineering [EMAIL PROTECTED]
Wellington - New Zealand +64 4 934-5856
===========================================================================
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".
