From my "CORBA days" I remember this is something you have to do by hand, i.e. code this "gateway" that maps your EJB interface to a more CORBA friendly interface. It's like developing any normal CORBA interface.
If there was an automatic way to do this then, I guess, the Java->IDL mapping would have been different!
My 2 cents
Thx for your post, but i guess this is not what i am looking for.
To make it more clear. Have a closer look at
As you can see there are 2 different ways to acces an EJB. But if you have to access an EJB with CORBA 2.0 ORBs then you have no chance with a so called "CORBA-Friendly EJB" except with wrapper. I am looking for a wrapper-plugin for application server or a possibility to write a wrapper, which can be deployed in an ejb.
Thanks for any help.
Had a quick look at the whitepaper, again, there are no magic solutions.
The wrapper framework looks more like a design proposal rather than an actual product you can use out of the box.
And it cannot be otherwise, because there is no good/simple Java(EJB) -> IDL mapping. You'll have to make some short of compromise and most of all design your EJB interfaces having IDL in mind.
This is my understanding