Date: 2004-08-13T17:59:56
   Editor: CraigMcClanahan <[EMAIL PROTECTED]>
   Wiki: Apache Struts Wiki
   Page: StrutsRelease122
   URL: http://wiki.apache.org/struts/StrutsRelease122

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -56,7 +56,14 @@
 
 '''??? Are the following flavours enough/appropriate ???'''
 
-(thusted: Ideally, we should be testing against the reference implementation for each 
supported platforms (Java 2.2 and Java 2.3), and rely on the the community to provide 
testing against whatever else they use. Since Tomcat is not the reference application 
anymore, I think inertia is the only reason we still use it for testing. Perhaps Craig 
could clarify what the appropriate RIs for Java 2.2 and 2.3 now are.
+  (thusted: Ideally, we should be testing against the reference implementation for 
each supported platforms (Java 2.2 and Java 2.3), and rely on the the community to 
provide testing against whatever else they use. Since Tomcat is not the reference 
application anymore, I think inertia is the only reason we still use it for testing. 
Perhaps Craig could clarify what the appropriate RIs for Java 2.2 and 2.3 now are.)
+
+  (craigmcc: Actually, Tomcat never has been the official RI for Servlet or JSP ... 
that role has
+  always been the J2EE Reference Implementation, now known as the
+  [http://java.sun.com/j2ee/1.4/download.html J2EE SDK].  That being said, Tomcat 
provides the
+  code used in this SDK, an Tomcat itself is likely to host the largest number of 
Struts apps,
+  so we clearly need to continue testing on it.  Anything additional is likely going 
to need to
+  be provided by the community.)
 
 Of course, testing against other containers would be great, but, realistically, we 
just don't have the committer resources to do more than test against the latest RIs.)
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to