[javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-16) Prune CORBA interoperability
- From: "Bill Shannon (JIRA)" <jira-no-reply@...>
- To: issues@...
- Subject: [javaee-spec issues] [JIRA] Commented: (JAVAEE_SPEC-16) Prune CORBA interoperability
- Date: Mon, 7 Jan 2013 23:30:52 +0000 (GMT+00:00)
- Auto-submitted: auto-generated
Bill Shannon commented on JAVAEE_SPEC-16:
It's very unlikely that we would introduce a new, standard, binary protocol
just for remote EJBs.
The choices seem to be:
1. Remove the requirement for CORBA interoperability while retaining
the requirement for remote EJB access. Implementations could meet
the requirement using a standard protocol such as CORBA or a
2. Remove the requirement for CORBA interoperability *and* remove the
requirement for remote EJB access. Implementations need not support
remote EJBs at all, but if they did they could use CORBA or some
As mentioned above, we expect that most remote access to EJBs is moving
to ReST using JAX-RS or SOAP using JAX-WS.
We understand the difficulty that removing any of these capabilities presents
to existing applications that depend on them, but we'd be very interested in
hearing of functionality required by new applications that is not provided
by JAX-WS or JAX-RS and would require new applications to choose the existing
remote EJB capability.
> Prune CORBA interoperability
> Key: JAVAEE_SPEC-16
> URL: http://java.net/jira/browse/JAVAEE_SPEC-16
> Project: javaee-spec
> Issue Type: New Feature
> Reporter: reza_rahman
> Although CORBA support in EJB was important once, CORBA usage has dropped
> precipitously in the past years in favor of REST and SOAP. Current CORBA
> use is so small that it makes the most sense to prune CORBA support going
> forward and significantly simplify EJB remoting.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira