jsr345-experts@ejb-spec.java.net

[jsr345-experts] Re: Pruning Corba (was Working draft documents are available for review)

From: Marina Vatkina <marina.vatkina_at_oracle.com>
Date: Tue, 05 Jul 2011 15:43:50 -0700

Adam,

If it becomes optional, as soon as in the next release, any app server
is free not to support it. Will it be OK with your integration purposes?

thanks,
-marina

Adam Bien wrote:
> CORBA works well, CMP not always :-). CORBA is good for integration
> purposes -> but I have nothing against pruning it. The leaner the
> standard, the better it is.
> On 04.07.2011, at 15:59, Antonio Goncalves wrote:
>
>> Hi,
>>
>> Pruning is really to make bits of the spec optional (like EJB CMP
>> that are now optional in Annexe). Why not do the same with Corba ?
>> I'm sure there are still projects that use Corba (as well as I still
>> know projects that use EJB CMP) but why not prune it in EE 7 and make
>> it optional in EE 8 ?
>>
>> The other day I was giving a Java EE 6 training course and 2 (young
>> students) never had heard of Corba.
>>
>> Antonio
>>
>> On Mon, Jul 4, 2011 at 13:26, Adam Bien <abien_at_adam-bien.com
>> <mailto:abien_at_adam-bien.com>> wrote:
>>
>> Hi Reza,
>>
>> I'm not sure about the pruning of CORBA. We are using CORBA in
>> some projects to access EJBs directly from C / C++. It works
>> really great.
>> CORBA seems to be also very popular in embedded space.
>>
>> +1 for making @DataSourceDefinition more usable,
>>
>> --adam
>>
>> On 30.06.2011, at 20:01, Reza Rahman wrote:
>>
>> > Marina,
>> >
>> > Good work (I am sure it was not particularly easy). I didn't
>> read everything word-for-word, but it looks OK. If I see anything
>> at a later point in time, I will let you know.
>> >
>> > Generally, it obviously makes things a lot less cluttered with
>> all the outdated stuff removed. I only regret that I did not push
>> harder to make all the EJB 2.x stuff pruned in EJB 3.1. Maybe we
>> can fix that this time. I don't know how others feel, but I would
>> also like to prune the CORBA interoperability. All this stuff was
>> fine in the late 90s/early 2000s. It's just an eyesore in
>> 2011/2012 and a reminder of why so many people still dread EJB
>> despite all of our efforts to make it a truly lightweight technology.
>>
>>
>>
>
>