[omniORB] generating persistent ior using GENIOR

[MICHEL Franck (SAGEM DEFENSE SECURITE)]

Hello,

We are trying to use "genior" to generate a persistent IOR :

genior "IDL:test:1.0" "192.168.0.1" "27300" ".MY_POA.MY_OBJECT_NAME"

The object_key used here is the one dumped from the server when :
- The server prints its IOR
- We decode it using "catior -o"
- We use the object key displayed here as a text
- We regenerate the IOR using "genior" and the text object key
=> no luck, it doesn't work

However, this generated ior doesn't work and the client cannot reach the server.

When we generate the persistent IOR using this alternative method, it WORKS :
- The server prints its IOR
- We decode it using "catior -x" (print object key as a hexadecimal value)
- We use the object key displayed here as an hex
- We regenerate the IOR using "genior" and the hex object key "0x..."
=> it WORKS

Any clue ?

We would like to use the text version as it seems less sensible to changes.

Besides, the IOR displayed by the server is different than the one generated with "genior" even with the hex trick.
Why ??




#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles ou ayant un caract?re priv?. S'ils ne vous sont pas destin?s, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque mani?re que ce soit le contenu. Si ce message vous a ?t? transmis par erreur, merci d'en informer l'exp?diteur et de supprimer imm?diatement de votre syst?me informatique ce courriel ainsi que tous les documents qui y sont attach?s."
******
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Frank MICHEL.vcf
Type: text/x-vcard
Size: 11312 bytes
Desc: Frank MICHEL.vcf
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20130222/7d45b061/attachment.vcf>

[Duncan Grisby]

On Fri, 2013-02-22 at 18:57 +0100, MICHEL Franck (SAGEM DEFENSE

Post by MICHEL Franck (SAGEM DEFENSE SECURITE)
genior "IDL:test:1.0" "192.168.0.1" "27300" ".MY_POA.MY_OBJECT_NAME"
- The server prints its IOR
- We decode it using "catior -o"
- We use the object key displayed here as a text
- We regenerate the IOR using "genior" and the text object key
=> no luck, it doesn't work

Those dots in the object key are not really dot characters. They are
representing unprintable binary values.

Post by MICHEL Franck (SAGEM DEFENSE SECURITE)
- The server prints its IOR
- We decode it using "catior -x" (print object key as a hexadecimal value)
- We use the object key displayed here as an hex
- We regenerate the IOR using "genior" and the hex object key "0x..."
=> it WORKS

By using the hex form, you have correctly handled the unprintable
characters.

Post by MICHEL Franck (SAGEM DEFENSE SECURITE)
Besides, the IOR displayed by the server is different than the one
generated with "genior" even with the hex trick.

There are padding bytes that are initialised with arbitrary data.

Why are you using genior to make your object reference? Why not just
use the IOR output by the server? Or use a corbaloc URI? genior is
meant as a testing and development tool, rather than something for
making persistent object references.

Duncan.