The JCP should spend most of its time evaluating which existing OSS framework/project is best and what may need to be contributed to that project to saticfy any JCP member concerns -- even forking if required. But re-creating the same conceptual framework in an slightly "improved" yet incompatible way is lame and just smacks of NIH syndrome.
Examples of things that should be JCP accepted "standards":
Spring & Spring MVC
Struts
Velocity
apache-commons stuff
-Bryan |
java.net RSS Feeds
