Please report new issues athttps://github.com/DOCGroup
A "resolver registry" is needed to allow services to dynamically register themselved with the ORB's resolve_initial_references() mechanism. The same registry could also be used for list_initial_services() and get_service_information(). The resolver registery would simply implement the Chain of Responsibility design pattern in much the same way TAO's pluggable protocol Acceptor Registry implements it.
Such a feature would be very useful for TAO's in-progress CORBA Security Service implementation.
Accepted.
The ORB::resolve_root_poa() method should be removed since it is a non-standard public method.
Nevermind. The resolve_root_poa() is an extension, but TAO has many other useful extensions. Removing it from the ORB interface just because it isn't a "standard" ORB method is not a compelling enough reason. Thanks to Irfan for pointing this out.
Ossama has almost completed this job, assing the bug to him so it can be clear when he commits the changes.
Close to being done.
It turns out this functionality is actually defined in the PortableInterceptor specification (see the "Dynamic Initial References" section). I'm going to hold off on any further implementation until we figure out if we're going to implement that feature.
The PortableInterceptor::ORBInitInfo::register_initial_reference() has been implemented, but there may still be some use for pluggable resolvers afterall.