Hello,
this is probably not feature but requirement. i.e. if your server is using
GIOP 1.0, MICO needs to "downgrade" and use also 1.0. Try to iordump your
server (ejb's) reference to get more information about what GIOP version
it uses.
Yes, I'm able to use exactly your parameters below to force client talking
with GIOP 1.2, but of course in case my server also talks with 1.2
Cheers,
Karel
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
---> http://www.objectsecurity.com/mico_commsup_referral.html <---
---
On Wed, 8 Mar 2006, Denis McHugh wrote:
Thanks Karel,
I am using mico 2.3.12, and it defaults to GIOP/IIOP version 1.0. I tried to
specify 1.2 as you advised, but I am not sure how to force the client to use
GIOP version 1.2.
I run the client like this:
client <client-specific args> -ORBGIOPVersion 1.2 -ORBIIOPVersion 1.2
-ORBDebug All
and in the debug output I see the following:
IIOP: [...] IIOP version 1.2
GIOP: [...] using GIOP version 1.0
I have attempted re-ordering the arguments, so that -ORBGIOPVersion is first,
last, etc but each time the GIOP version is 1.0. Is this a known issue ?
Thanks again,
Denis.
Hello,
what GIOP/IIOP are you using on MICO side? Perhaps you might try 1.2 forced
by -ORBGIOPVersion 1.2 -ORBIIOPVersion 1.2 command-line parameters.
Yes, JBoss developers used MICO to invoke EJBs operations from C++.
Cheers,
Karel
PS: If you are not using MICO 2.3.12, also please make sure you test it
--
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee?
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel
