LifeCycle Factory Finder

[Scott T. Prugh]

From the LifeCycle spec, I assume that every executable that wants to
participate in LifeCycle operations should provide the FactoryFinder
interface. Is this a correct assumption? How is(or would this be)
implemented in any commerical ORBs.

Scott.

[Lee Sailer]

I don't think so. At least one FactoryFinder object will be needed, so
only one executable needs to provide one (though more is OK).

As I recall, copy() and move() take a FF argument. That FF is
responsible for doing the new object construction, etc. Now, to be a
destination of a copy or a move, an executable that implements the "new"
object will almost certainly include a Factory that the FF knows about.
Thus, the FF can use the F to copy().

--
ZZ

[Kolli Chakravarthy]

Scott T. Prugh wrote:
>
> From the LifeCycle spec, I assume that every executable that wants to
> participate in LifeCycle operations should provide the FactoryFinder
> interface. Is this a correct assumption? How is(or would this be)
> implemented in any commerical ORBs.
>

> Scott.

No. You will see one implementation of the factory finder interface. My
guess is ORB vendors will provide an implementation for the factory
finder an let you register/unregister your factories with it.