[jsr342-experts] Pruning JSR-77

From: Jason T. Greene <jason.greene_at_redhat.com>
Date: Mon, 10 Oct 2011 09:25:14 -0500

We skipped pruning JSR-77 last time around because a number of us
thought it was better to update it to be more current. I think it's
become clear that the spec is not only not going to be updated, but that
its relevance is fading with the cloud direction the industry is moving in.

Can we prune it this time around (make it optional to vendors)? Also,
why does the pruning process require that we wait for the next EE
iteration to finalize something being made optional? Let's assume that
in this example we made JSR-77 optional in EE7, then after 7 is released
we decided it was a mistake, we can just bring it back as required in EE8.

Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat