As I understand it Corba objects can call EJBs via RMI-IIOP which is
supported not at the server level (Orion) but by the VM. Didn't RMI-IIOP
become standard with the JDK 1.3?
The limitation is that you can not run a Corba object as an EJB so that you
could make outbound Corba calls from your app server and use Orion or other
as a Corba object server. If you want to do that you will have to use
Inprise's App server which is built upon the Visigenics Corba Orb.
But I don't know if you are asking specifically about the use of an Orb.
It appears as though you are trying to just implement the Trader Service
with EJB much like the OMG specified Corba Trader Service.
If this is the case you could use RMI to communicate with a specific EJB
server to query for all of the Objects and home interfaces as well as JNDI
locations of resources within your service range (Corba guys call the
service range a federation). Then you could have one location in an
enterprise that could be querried for available services even though the
services might reside on different machines and different networks within
the enterprise.
Cory
At 10:33 PM 11/10/00 +1100, James Ho wrote:
>Hi there.
>
>What I am doing for a project, to allow different service providers to
>join my central service. Each of the service providers would have to
>implement a Bean wiht the home and remote interface specified by the
>central service, and the central service uses EJB to communicate with
>those servers...it is rather a dynamic system....Thus the central
>service would be likely to interact with many DIFFERENT type of app
>servers. As of your client jars suggestion, do u mean the client
>proram the bean..'jar' it, and send it to the central service?
>
>ORB? then I'd have to touch CORBA then? and ORB acts as a wrapper to
>my bean? If so, why EJB?
>
>If I use a separate LDAP for the service providers to deployed their
>bean at...would that solve the problem?
>
>Thanks :)
>
>James.
>
>
>>you can't... yet (No IIOP in Orion yet)
>>and mostly, what IIOP(Internet Inter-ORB Protocol) provides is ORB
>>communication,
>>the ORB (Object Request Broker) is the one that provides your beans
>>services, and provides
>>beans to its clients...
>>
>>In an EJB architecture, it may be easy to implement distrubuted
>>transactions, for instance, thanks to IIOP + 2PC commit/ OpenXA
>>transactions, but applying security (which is server specific) can become
>>hell
>>
>>Also, if the JNDI of a given server doesn't support it, it can be tricky to
>>code the beans;
>>
>>My advise is to create/obtain client jars which are mainly the remote & home
>>interfaces;
>>Always narrow Objects >>PortableRemoteObject.narrow (MyBean.Class)<<
>>
>>Perhaps if you elaborate further the List may be of assistance
>>
>>HTH,
>>
>>JP
>>
>>(P.S.: I hope you don't want to interact with Oracle App Servers, OAS or
>>IAS... for the mission isn't hard, it's just impossible ;-)
>>
>>-----Original Message-----
>>From: James Ho [mailto:[EMAIL PROTECTED]]
>>Sent: Viernes, 10 de Noviembre de 2000 13:19
>>To: Orion-Interest
>>Subject: Re: URGENT: talking with other app server?
>>
>>
>>"Juan Lorandi (Chile)" wrote:
>>>
>>> To connect different App servers (diff vendors) IIOP will be used
>>>
>>
>>How can I do that with Orion?
>>
>>James
>>
>
>
>
