The Apache/Sun Relationship Worsens
d6y writes "Over on the O'Reilly weblogs there's an entry on the relationship between Sun's Java Community Process and Apache. Sun have been rubbing people up with wrong way (the problems of licensing open source J2EE containers; stuts v. JavaFaces; log4j v. JDK 1.4 logging....) and I hope this gets sorted out real soon.
See also the original VNUNet article and Apache's position paper."
I am sure that everyone here has met an MCSE (or other certified) bonehead who passed the tests but couldn't do system administration in a real world setting to save his life.
Now admittedly Sun's requirements for J2EE certification are a bit more stringent than those required for becoming an MCSE. But certification can only get you so much. The proof is ultimately in your product. JBoss has received so much attention lately because it is a solid, robust product. The attention paid to its lack of certification quite simply distracts from this.
Certification is a way for Sun to revamp costs. I don't have a problem with that at all. Lack of certification for JBoss probably means that it won't be used on many enterprise systems for the time being, but that will (and is) changing as it continues to evolve. In the meantime, JBoss will succeed or fail in the marketplace on its own merits. And if and when it does reach "critical mass", it will be all the sweeter because this will have been an uphill battle for the entire JBoss team.
- Rev.If Sun's antics are making you ill, why not help out the folks at Ximian on Mono? It is backed by a REAL ECMA standard and not controlled by one company. Sure it's based on an MS product, but at least MS had the balls to submit it to a standards body and NOT retract it.