Jim Knutson wrote on 07/18/11 08:53 AM:
> Linda DeMichiel <linda.demichiel_at_oracle.com> wrote on 07/15/2011 07:51:26 PM:
> > In Java EE 6 we identified the following technologies as candidates
> > for pruning, marking them as "Proposed Optional":
> > JAX-RPC
> > JAXR
> > Java EE Deployment
> > EJB Entity Beans
> >
> > ...
> >
> > To avoid any backtracking on the part of EJB 3.2, I would prefer to
> > decide at this point which of the Proposed Optional technologies
> > listed above should be designated as Optional as of Java EE 7. We
> > would prefer that all of you express a position on this so that we can
> > best evaluate the extent to which there is consensus.
>
> I'm in favor of making them all optional, though at some point I'd like to
> have a discussion on whether optional features should be optional or
> completely removed.
What would "completely removed" mean to you?
You can completely remove the optional features from your product.
For most optional features where an entire spec is made optional,
the only mention of the optional feature will be in the platform
spec.
The RI will continue to provide the optional features.
We've discussed ways to mark the javadocs so that it's more clear
which technologies are optional in the context of the platform,
but we haven't found a good solution yet.
What problem would be solved by "completely removing" these technologies?
Perhaps there are other ways to solve that problem?
Since we're using the pruning process defined by the Java SE group,
any change to the process should be coordinated with them.