"Cakalic, James" wrote: > Hmm. Just because it appears in the JDK doesn't mean that it is a "good > thing".
<snip> > As a user of Struts, imagine > for a moment that JDK 1.5 included an MVC implementation similar to Struts > but with reduced functionality and limited extension capability. Would you > switch just because it was included in the JDK? Good example ! Any code base that implements another code base is, by definition, limited and frozen in time, as a requirement of implementing it. For example, as much as I enjoy the productivity of Expresso, as a Struts implementation it is a 1.0, or whatever version the contributors implement for that release of Expresso that I am using at the time. :( Another example is SOAP, which I would like to use one of Apache's versions. But without all the potential parser conflicts worked out between versions of SOAP, Tomcat, Xerces, etc, it can be a challenge. So I am trying Apache XmlRpc instead, for the moment. The blessings of a wealth of open source tools...... Really makes one consider the way Jboss has used JMX to keep the interfaces all clean. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
