I believe the Watchdog parts are the compliance tests.
As for HOW vendor Y implements a feature, I doubt you would know unless you
decompiled it, which would be illegal. All you really care about is that a
spec feature is implemented, not HOW. A reference implementation is refered
to when the spec alone is not crystal clear and an example of how the
feature is to react is needed.
As to the production quality, if a vendor can't cut it against Tomcat, then
they wont have clients. They may have clients if their full stack is there
and very well intergrated. Isn't that part of what OSS means to companies?
It is also one of the reasons Apache is so popular, not because it is free,
but because it is so darn good.
Thor HW
----- Original Message -----
From: Stark, Scott (Exchange) <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 16, 2000 8:05 AM
Subject: Re: Tomcat-as-a-reference implementation?
> I agree with this logic from a vendors perspective. Conformance should be
> based on a well defined compatability test suite and any servlet engine
> vendor can measure themselves against. Does such a test suite exist?
>
> -----Original Message-----
> From: Vince Bonfanti [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 16, 2000 9:26 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Tomcat-as-a-reference implementation?
>
>
> Yes, I'm concerned about this from the perspective of the vendor of a
> servlet/JSP engine that strives to faithfully implement the specs. My
> concern is that people will apply the following logic to non-spec
features:
>
> 1. Tomcat is the Reference Implementation of servlets/JSP.
> 2. Tomcat implements Feature X.
> 3. Vendor Y's servlet engine doesn't implement Feature X, or
implements
> it differently than Tomcat.
> 4. Therefore, Vendor Y's servlet engine isn't spec-compliant.
>
>
> ***********************************************************************
> Bear Stearns is not responsible for any recommendation, solicitation,
> offer or agreement or any information about any transaction, customer
> account or account activity contained in this communication.
> ***********************************************************************
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
