But you have to understand, the CTS is a "one-way" test. That is to say,
using the below example, that as long as that said app server allowed the
empty collection, it would never check the boundry for a null collection
working. I do not believe it is the job of the cts to do such boundry
checking. That would stagnate vendors from making either enhancements, or
backwards compatability. To a degree it is the developers onus to
understand the spec, and what portability truly means. Now that said, I can
empathise with the developer community, and hence my position on releasing
implementations of incomplete and changing specifications. But thats the
fault of a vendor not the cts.
Dave Wolf
Internet Applications Division
Sybase
----- Original Message -----
From: "Wong Kok Wai" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 10:01 AM
Subject: Re: Null or empty collection
> 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".
>
>
===========================================================================
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".
