Re: IOR reference of ORbit2 not recognized by mico

[Mark McLoughlin <mark skynet ie>]

Hey,

On Wed, 20 Mar 2002, Hing-Wah Wan wrote:

> >From the output of ior-decode-2 :
> Object ID: IDL:omg.org/CosNaming/NamingContextExt:1.0
> IOP_TAG_GENERIC_IOP: GIOP 1.2[UNIX]
> hingwah:/tmp/orbit-hingwah/linc-29a19f5586230
>
> IOP_TAG_INTERNET_IOP: GIOP 1.2 hingwah:33014
>     object_key (24) '000000003ba9eb0f4398b0c50100000047f8e840333a6774'
>
>  IOP_TAG_ORBIT_SPECIFIC: usock /tmp/orbit-hingwah/linc-29a19f5586230
>     IPv6 port 0
>     object_key (24)
> '000000003ba9eb0f4398b0c50100000047f8e840333a6774'
>
> IOP_TAG_MULTIPLE_COMPONENTS:
>     IOP_TAG_COMPLETE_OBJECT_KEY: object_key (24)
>     '000000003ba9eb0f4398b0c50100000047f8e840333a6774'
>
>         Unknown component 0x1
>        ^^^^^^^^^^^^^^^^^^^^^
> from the response in the mico mailing list,
> it seem that mico fail to recognize the IOR because of this unknown
> component ,bugs?

	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.

Good Luck,
Mark.