[omniORB] Need a special omniINSPOA

[Wernke zur Borg]

Thank you, Duncan. I will try to follow that suggestion.

Wernke

> -----Original Message-----
> From: Duncan Grisby [mailto:duncan at grisby.org] 
> Sent: 13 January 2006 12:49
> To: Wernke zur Borg
> Cc: omniorb
> Subject: Re: [omniORB] Need a special omniINSPOA
> 
> On Thursday 12 January, "Wernke zur Borg" wrote:
> 
> > for a special case I need a POA that behaves like 
> omniINSPOA but only
> > with a different thread policy. In particular, it must have 
> the USER_ID
> > policy and it must create "simple" object keys, so that the 
> objects can
> > be located with a corbaloc URI.
> > 
> > Whenever I try to create an own child POA with USER_ID 
> policy, it does
> > not use simple keys, thus the object cannot be found in the object
> > table.
> > 
> > How can I achieve the "special" behaviour of the omniINSPOA 
> with respect
> > to the object keys created?
> 
> You can't, unless you feel like modifying the policies that the
> omniINSPOA has when it is created in the ORB core.
> 
> What I suggest you do is to register an object in the omniINSPOA with
> the key you want that raises omniORB::LOCATION_FORWARD, 
> redirecting the
> client to an object in a POA with the policies you want. That has the
> additional advantage that important things that are stored in 
> IORs, like
> code set conversion info, are sent in the location forward.
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby         --
>   -- duncan at grisby.org     --
>    -- http://www.grisby.org --
>