[omniORB] interoperability of DII requests

[Ridgway, Richard (London)]

Give this a whirl in your jacorb.properties.
	jacorb.log.default.verbosity=3
	jacorb.debug.dump_incoming_messages=on
Gets quite verbose, and helps to have the giop spec to hand, but has
been useful a few times to me. JacORB 2.3.0 and omnORBpy work fine
together, although I don't use DII.

Richard

-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Duncan
Grisby
Sent: 06 July 2007 21:26
To: Jason Stelzer
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] interoperability of DII requests 


On Friday 6 July, Jason Stelzer wrote:

> I can connect to the jboss server and lookup the remote name service
> on the C++ side.
> 
> I can lookup objects and create requests. However, I believe I'm
> either putting the request together wrong or need to declare things
> slightly differently.

I haven't looked in detail at your code. Are you sure you're filling in
the right request for the parameters the server is expecting?

I'd suggest first trying a static invocation based on the IDL, to
confirm that that works, before dealing with the complexity of DII. If
you can possibly avoid it, it's best not to use DII at all. It's just so
much extra work.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --

_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------