AW: [omniORB] activate_object_with_id Returns None

Marco Ferreira mferreira at devion.org
Thu Apr 24 17:51:48 BST 2008


Hey Fischer.

interface_inst_list is a dictionary like: { 'servant_name': servant_object }

Therefor the usage: poa.activate_object_with_id(servant, interface_inst_list[servant])


I'm using it correctly, right?


Michael:

Would it work if the endPoint is defined at omniORB4.cfg ?


Fischer, Clemens wrote:
> Hi Marco,
>
>  
>
> take a closer look at activate_object_with_id.
>
> The first parameter must be an object id string, the second one a
> servant object (a python object).
>
>  
>
> Cheers
>
> Clemens
>
>  
>
> ________________________________
>
> Von: omniorb-list-bounces at omniorb-support.com
> [mailto:omniorb-list-bounces at omniorb-support.com] Im Auftrag von Marco
> Ferreira
> Gesendet: Donnerstag, 24. April 2008 17:29
> An: Michael
> Cc: omniorb-list at omniorb-support.com
> Betreff: Re: [omniORB] activate_object_with_id Returns None
>
>  
>
> Sorry, I can't do that since it's corporate material.
>
> I've re-written my code again to handle the omniINSPOA, here's a sample
> of the code:
>
>     poa = orb.resolve_initial_references("omniINSPOA")
>     poa._get_the_POAManager().activate()
>  
>     base_service_inst = BaseService_i(poa, client_orb)
>     (...)
>     log.debug("Activating objects:")
>     for servant in interface_inst_list:
>         log.debug(" ...%s"% servant)
>         poa.activate_object_with_id(servant,
> interface_inst_list[servant])
>     
>     # Block for ever (or until the ORB is shut down)
>     orb.run()
>
>   




More information about the omniORB-list mailing list