Re: IOR reference of ORbit2 not recognized by mico

[Duncan Grisby <dgrisby uk research att com>]

On Wednesday 20 March, Mark McLoughlin wrote:

> 	If mico doesn't recognise a component, it should ignore it.
> There is enough info in the other components for mico to connect to
> the object.

The IOR is invalid. Try giving it to

  http://www.parc.xerox.com/istl/projects/ILU/parseIOR/

and you get

...
(iiop.c:parse_MultiComponent_Profile):  profile contains 2 components
(iiop.c:parse_MultiComponent_Profile):  component 1 of type 5, 24 bytes
Attempt to read byte sequence of length 83951617, which exceeds
IIOPMaxStringSize value of 4294967295 or call limit of 65535.
(iiop.c:parse_MultiComponent_Profile): Invalid encapsulated profile
detected:

omniORB 4's catior agrees that it's invalid, but doesn't give such a
helpful error message. (omniORB 3 and earlier don't try to look into
multiple component profiles, so they don't notice that it's invalid.)

The second component of the multiple component profile claims that it
has a marshalled length of 83951617 octets, which it clearly doesn't,
so MICO et al are quite right to complain that the IOR is invalid.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --