[mico-devel] MIwCO AB and TB error

[Karel Gardas]

Hi Jaakko,

sorry for delay. I'm not sure, but we've merged SecurityLevel3 support 
into post-2.3.12 development tree and if this is what is used in a test, 
then SL3 also brings ObjectCredentialsPolicy implementation which required 
some changes to be done also in a way how ORB handles IORs. The OCP is 
usable to have only certain information in generated object IOR. As this 
is POA's policy and POA needs to be able to generate "restricted" IOR, I 
changed the POA to clone ORB's IOR template instead of just using it. i.e. 
we need "unrestricted" IORs on another POAs w/o OCP... Perhaps this might 
cause your issue?

Thanks,
Karel

On Sat, 26 May 2007, Jaakko Kangasharju wrote:

> Between these two lines, add the code
>
>        if (i == 0)
>            _orb->ior_template()->active_profile(prof);
>
> It seems like this should work.  However, I'm a bit puzzled as to why
> I never saw this problem because it should manifest itself on every
> run, and I did test the wireless parts with 2.3.12 at some point.
>
> Karel, if you're following, did something change recently in how the
> IOR class handles its active_profile member?  It seems like
> del_profile will set it to NULL when it's deleted, and add_profile
> does not set it even when it's adding the first profile.  This seems
> to me to be the cause of this problem, since a MIWCO bridge starts by
> deleting all profiles from the IOR template.

--
Karel Gardas                  kgardas at objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com