|Eclipse and Corba [message #493977]
||Wed, 28 October 2009 12:08
Registered: October 2009
Sorry, this is not the right place for this question:
1) ORB and Server running on a machine using eclipse.
2) Client running to second machine eclipse...
now in this case how can client request is processed.
Are their any step I need to configure to achieve this communication?
|Re: Eclipse and Corba [message #494252 is a reply to message #493977]
||Thu, 29 October 2009 14:09
| Scott Lewis
Registered: July 2009
> Sorry, this is not the right place for this question:
> 1) ORB and Server running on a machine using eclipse.
> 2) Client running to second machine eclipse...
> now in this case how can client request is processed.
> Are their any step I need to configure to achieve this communication?
This is not quite the right place for this question...although I don't
really have a better place to recommend for you, so I'll provide the
information I can.
Eclipse is based upon OSGi/Equinox , and OSGi has a
classloader-per-bundle model for classloading. RMI has a different
model of classloading...which is not the same as the
classloader-per-bundle model...and this creates some difficulties (i.e.
see  and  for some info that I found searching for osgi and corba).
Java's RMI has a corba implementation built in, I believe, but I suspect
that since RMI's classloading model doesn't match the
classloader-per-bundle model of RMI...and that this would create some
difficulties in setting up/using the RMI implementation of corba within
Eclipse (or any OSGi runtime environment).
Having said that, it's probably quite possible that one could create an
ECF remote services provider based upon/using some corba
implementation(s)...and we do have old code that implemented a provider
based upon RMI. Here's info about ECF's remote services API ...in
short it's a protocol-independent API for doing remote OSGi
services...and so rmi/corba/others can/could be the underlying
communication for a provider that implemented the remote services API.
Note we've already got providers based upon: tcp (called generic),
xmpp, JMS/ActiveMQ, skype, javagroups, and others).
Hope this helps. If you are interested in/able to work on/contribute
work on a corba-based ECF provider please consider joining the ecf-dev
mailing list  and making the desire known. There may be others in
the ECF dev community that either would like the same thing...or perhaps
have even made technical steps in those directions.
 http://www.eclipse.org/equinox/ and http://www.eclipse.org/ecf
 http://email@example.com/msg00015. html
 http://firstname.lastname@example.org/msg00021. html
Powered by FUDForum
. Page generated in 0.01786 seconds