To: Charles Tutt who wrote (59886 ) 7/16/2001 6:20:55 PM From: keithsha Respond to of 74651 IBM WebSphere, the largest J2EE installed base was slow to release EJB 2.0 (> 1 year) Oracle is ignoring EJB Entity beans in favor of an Oracle-specific model BEA is pursuing Web Services independently of J2EE J2EE is not easily portable due to vendor extension required by the incompleteness of the spec Extensions to EJB make apps non-portable - IBM’s 268 page document on how to port from BEA Weblogic to WebSphere Mark Driver, Gartner “The primary drawback to new generation comprehensive toolsets [for J2EE] will inevitably be a degree of vendor lock-in.” - in an October 2000 Research Note on Java. Thomas Murphy, Forrester “...[the Java] platforms' proprietary infrastructure services (e.g., workflow, messaging, persistence, legacy integration) will create substantial barriers to application portability.” - December 2000 Mike Gilpin, Giga “…products delivered to market are often a combination of standards and other added capabilities that fall outside the definition of the standard.” – December 2000 And Java as the only language you can code in on J2EE has some serious flaws In one recent poll of developers, devx.com , July 2000, 90% of respondents said they used more than one development language. Fully 69% said they used 3 or more languages. Many other criticisms of Java as a language at geocities.com Net net: "We do not support Sun's decision to withdraw from the standards process. We had hoped that this second attempt to create a Java standard, via ECMA (European Computer Manufacturing Association), would proceed rapidly and secure a Java standard for the software developer community. We believe a standards process managed by a single vendor will not work in the long-term." -Rod Smith, Vice President, Java Software, IBM In an open letter titled, "IBM's position on open standards and J2EE" Appearing December 23, 1999. Or you could just listen to me :-) keithsha