Imre, I don't know if I would give up the fight yet.
Earlier, you said:
>The issue boils down to resource management. We view bean instances as
>reusable resources and have applied the same resource management
>principles to them as to all the other shared resources we manage in our
servers.
>Guaranteeing a consistent and predictable state for all pooled resources
>is crucial for a robust and scalable server implementation.
IMHO, your approach is right, and the spec should change, perhaps adding
a <container hands off> section to an XML deployment descriptor. The
containers
would, by default, reset fields that were not in this section, when a bean
is
cycled back to the free pool.
OTOH, who really needs a robust, scalable system, anyway? :)
===========================================================================
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".
