[omniORB] BIDIR and others

[Corrigan Coleman]

I've had a similar problem with corbaloc when resorting to the UTF-8
Codesets. Try specifying the iop version,
e.g.   InitRef = NameService=corbaname::1.2@myhost.com:

-----Original Message-----
From: Yarigin S [mailto:yarigin@protvino.systel.ru]
Sent: 14 April 2003 07:56
To: omniorb-list@omniorb-support.com
Subject: [omniORB] BIDIR and others


Hello,
Is anyone use bidirectional connections with omniORB?
I have a problem:
Version 401, platform win2000,win98,compiler VS6+sp5.
Client and server has both bidir properties enabled( TransportRules, POA 
policies, offer/accept).
trouble 1:
Client make a connection to omniNames to receive ref to server.
In 90% (but not pure 100%!?) the exc. "GIOP 1.2 error" thrown at 
_narrow() of NamingContext.
trouble 2:
If client try to resolve server reference directly by corbaloc name ( 
server has persistent policy and user id) the same exception is thrown 
when _narrow() server object.

In debuger it seen that server send a reply with GIOP 1.0 type while in 
GIOP 1.2 mode.
-----------
Second problem:
POA policy user_id could not be used with corbaloc if object is not in 
root POA. Id received from corbaloc has name separator '/' but id stored 
in active objects table has separator '0xFF' and has extra separator at 
beginning.

Sergey Y.

_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
************************************************************************
This e-mail and any files transmitted with it are confidential and may be
privileged and are intended solely for the individual named/ for the use of
the individual or entity to whom they are addressed.If you are not the
intended addressee, you should not disseminate, distribute or copy this
e-mail.Please notify the sender immediately if you have received this e-mail
by mistake and delete this e-mail from your system.If you are not the
intended recipient, you are notified that reviewing, disclosing, copying,
distributing or taking any action in reliance on the contents of this e-mail
is strictly prohibited.Please note that any views or opinions expressed in
this e-mail are solely those of the author and do not necessarily represent
those of Traventec Limited.E-mail transmission cannot be guaranteed to be
secure or error-free as information could be intercepted, corrupted, lost,
destroyed, or arrive late or incomplete.Traventec Limited therefore does not
accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail transmission.The recipient should
check this e-mail and any attachments for the presence of viruses.This
e-mail has been swept for computer viruses however Traventec Limited accepts
no liability for any damage caused by any virus transmitted by this e-mail.