[omniORB] Implementation repository ?

[Roger Barnett]

--0__=F1gE4bvU03BV2S5di8X1mkXERma39shieA7pvK9UieMbz3s2ntozeDcW
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline





Joan Ramon L
--0__=F1gE4bvU03BV2S5di8X1mkXERma39shieA7pvK9UieMbz3s2ntozeDcW
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-transfer-encoding: quoted-printable


=F3pez Gillu=E9 writes:
>
> Does anybody know whether there's any implementation of a CORBA
> Implementation Repository that works with omniORB?

There is no such thing as a CORBA Implementation Repository. Some ORBs
do provide tools (often referred to as daemons) but this is not part of=

any specification - or indeed a requirement for many applications.

As there are no standards to follow you can write your own either as a
general tool or specific to your own requirements; I'd recommend writin=
g
a Location Broker as a normal ORB-based service rather than trying to
hook into the internals of a specific ORB.


Having said this, there is actually an OMG specification in this area
that is worth looking at, the Object Reference Template Specification
(the latest reference I have is orbos/01-04-03, but as it now has final=

 status there should be a later one).

This spec has several things to say about _interfacing to_ activation
mechanisms, so if you do decide to roll your own read this first.


Roger Barnett
=

--0__=F1gE4bvU03BV2S5di8X1mkXERma39shieA7pvK9UieMbz3s2ntozeDcW--