I'm more concerned with the CTS which, from experiences of using a rather famous
app server, does not uncover all the portability issues.
Dave Wolf wrote:
> But this goes back to my point on releasing specs early is not a good thing
> or in the communities interests. See the early public drafts of EJB 1.1
> still had the confusing phrasing of saying a "null collection" was returned.
> Some containers (Ill be polite) who released EJB 1.1 early implemented this
> as per the confusing phrase, this allowing you to return a null collection
> rather then an empty collection. This caused developers to implement their
> finders illegally by returning null collections, leading to big portability
> issues. I still contend that releasing implementations of specifications
> before they are final is a dis-service to the community. Developers should
> be very aware that by implementing applications early using containers with
> partial, pre-released implementations of a specification put them at a
> significatn portability risk. Since one of EJB's biggest advantages is
> portability, you should approach such pre-release implementations with care
> and forethought.
>
> Dave Wolf
> Internet Applications Division
> Sybase
>
===========================================================================
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".
