[omniORB] Re: omniORB-list Digest, Vol 7, Issue 6
Peter Van Osta
pvosta at unionbio-eu.com
Fri Nov 7 14:57:34 GMT 2003
Hi,
Thank you booth for the information, we will take a look at it for
creating the ".dll"s for the MS-Windows client.
Best regards,
Peter Van Osta
Union Biometrica N.V./S.A.
European Scientific Operations (ESO)
Cipalstraat 3
B-2440 Geel
Belgium
Tel.: +32 (0)14 570 620
Fax.: +32 (0)14 570 621
http://www.unionbio-eu.com/
http://ourworld.compuserve.com/homepages/pvosta/cvwww.htm
================================================
omniorb-list-request at omniorb-support.com wrote:
> Send omniORB-list mailing list submissions to
> omniorb-list at omniorb-support.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> or, via email, send a message with subject or body 'help' to
> omniorb-list-request at omniorb-support.com
>
> You can reach the person managing the list at
> omniorb-list-owner at omniorb-support.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of omniORB-list digest..."
>
>
> Today's Topics:
>
> 1. only part of giop message was send. (zhanhai)
> 2. omniORB client to ORBit server (Peter Van Osta)
> 3. Re: How to realise colocation (maybe w/o POA)? (W. Borgert)
> 4. Re: omniORB client to ORBit server (baileyk at schneider.com)
> 5. Re: omniORB client to ORBit server (Duncan Grisby)
> 6. Re: only part of giop message was send. (Duncan Grisby)
> 7. Re: POA::deactivate_object and id_to_reference (Rene Jager)
> 8. RE: Reverting object reference to original profile ques tion
> (Lee, Robert C.)
> 9. Re: omniORB 4.0.3 soon (Serguei Kolos)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 6 Nov 2003 20:20:56 +0800
> From: "zhanhai" <sea2000 at gxlu.com.cn>
> Subject: [omniORB] only part of giop message was send.
> To: <omniorb-list at omniorb-support.com>
> Message-ID: <04a301c3a460$6e01c010$660310ac at SEA>
> Content-Type: text/plain; charset="gb2312"
>
> When we try to call operation of object provided by java implemented server,using jacorb as the ORB, from our omniorb based application,
> only part of giop message was send out. Then the server side keeps waiting for the remain message while omniorb considered the whole message was send out and no more message will be posted .
>
> Following is the original message send out by omniorb:
> ll_send: 62 bytes
> 4749 4f50 0100 0003 0000 0032 0000 0001 GIOP.......2....
> 0000 002a 5374 616e 6461 7264 496d 706c ...*StandardImpl
> 4e61 6d65 2f4c 7563 656e 7450 4f41 2f11 Name/LucentPOA/.
> 2a39 4d06 163c 1918 0125 404a 2234 *9M..<...%@J"4
>
>>From the message, we can see only 'messageheader' + 'object key' was send, other fields such as 'operation name' and 'arguments' disappeared.
>
> We are using omniorb 3.0.4 for hpux11.0.
> Any suggesstions ?
>
> Thanks
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20031106/581d722e/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Thu, 06 Nov 2003 13:43:25 +0100
> From: Peter Van Osta <pvosta at unionbio-eu.com>
> Subject: [omniORB] omniORB client to ORBit server
> To: omniORB list <omniorb-list at omniorb-support.com>, ORBit list
> <orbit-list at gnome.org>
> Message-ID: <3FAA41ED.7080006 at unionbio-eu.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Hi,
>
> I would like to connect an omniORB client running on MS-Windows 2000 and
> XP to an ORBit server running on RedHat Linux 7.x and 8.x.
>
> I have read that omniORB can be used in MS Visual C++ 6.x ? Could we
> build a ".dll" which we could provide to a customer to build his own
> application and let them use use the ".dll" or do we have to provide the
> IDL-file for them to compile themselves.
>
> Best regards,
>
> Peter Van Osta
>
> Union Biometrica N.V./S.A.
> European Scientific Operations (ESO)
> Cipalstraat 3
> B-2440 Geel
> Belgium
> Tel.: +32 (0)14 570 620
> Fax.: +32 (0)14 570 621
>
> http://www.unionbio-eu.com/
>
> http://ourworld.compuserve.com/homepages/pvosta/cvwww.htm
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 6 Nov 2003 14:42:59 +0100
> From: "W. Borgert" <debacle at debian.org>
> Subject: Re: [omniORB] How to realise colocation (maybe w/o POA)?
> To: "Duncan Grisby <duncan at grisby.org>; gduzan"@bbn.com
> Cc: omniorb-list at omniorb-support.com
> Message-ID: <1068126179.3faa4fe3eb98b at webmail.in-berlin.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thanks Gary, thanks Duncan. We will work without "shortcut" for now
> and only use it if anything else (optimisation) fails. Cheers!
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 6 Nov 2003 08:10:07 -0600
> From: baileyk at schneider.com
> Subject: Re: [omniORB] omniORB client to ORBit server
> To: pvosta at unionbio-eu.com
> Cc: ORBit list <orbit-list at gnome.org>, omniORB list
> <omniorb-list at omniorb-support.com>
> Message-ID: <OF0B9E804F.09CA3384-ON86256DD6.004D5746 at schneider.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> Please see
>
> http://www.omniorb-support.com/pipermail/omniorb-list/2003-October/024387.html
>
> which is a post I made recently on building a DLL from omniORB stubs. Of
> course you will still need to give your customer your IDL, or equivalent
> documentation of your interfaces. The generated header files are not the
> best form of documentation for your DLLs.
>
> You may also want to read
>
> http://www.omniorb-support.com/pipermail/omniorb-list/2003-October/024392.html
>
> which clarifies some details.
>
>
> Kendall
>
>
>
>
>
> Peter Van Osta
> <pvosta at unionbio-eu.com> To: omniORB list <omniorb-list at omniorb-support.com>, ORBit list
> Sent by: <orbit-list at gnome.org>
> omniorb-list-bounces at omniorb- cc:
> support.com Fax to:
> Subject: [omniORB] omniORB client to ORBit server
>
> 11/06/2003 06:43 AM
> Please respond to pvosta
>
>
>
>
>
>
> Hi,
>
> I would like to connect an omniORB client running on MS-Windows 2000 and
> XP to an ORBit server running on RedHat Linux 7.x and 8.x.
>
> I have read that omniORB can be used in MS Visual C++ 6.x ? Could we
> build a ".dll" which we could provide to a customer to build his own
> application and let them use use the ".dll" or do we have to provide the
> IDL-file for them to compile themselves.
>
> Best regards,
>
> Peter Van Osta
>
> Union Biometrica N.V./S.A.
> European Scientific Operations (ESO)
> Cipalstraat 3
> B-2440 Geel
> Belgium
> Tel.: +32 (0)14 570 620
> Fax.: +32 (0)14 570 621
>
> http://www.unionbio-eu.com/
>
> http://ourworld.compuserve.com/homepages/pvosta/cvwww.htm
>
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>
>
>
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 06 Nov 2003 14:32:41 +0000
> From: Duncan Grisby <duncan at grisby.org>
> Subject: Re: [omniORB] omniORB client to ORBit server
> To: pvosta at unionbio-eu.com, ORBit list <orbit-list at gnome.org>, omniORB
> list <omniorb-list at omniorb-support.com>
> Message-ID: <200311061432.hA6EWf232184 at grisby.dyndns.org>
>
> On Thursday 6 November, baileyk at schneider.com wrote:
>
>
>>http://www.omniorb-support.com/pipermail/omniorb-list/2003-October/024387.html
>>
>>which is a post I made recently on building a DLL from omniORB stubs. Of
>>course you will still need to give your customer your IDL, or equivalent
>>documentation of your interfaces. The generated header files are not the
>>best form of documentation for your DLLs.
>>
>
> That is true if you want to package up _just_ the output from the IDL
> compiler into a DLL. However, if what you want to do is package up the
> client code itself, as well as the generated stubs, into a single DLL,
> there is no need for any of that. You just link the stub sources into
> your DLL and it will all work fine.
>
> What do you actually want to have in your DLL?
>
>
>>http://www.omniorb-support.com/pipermail/omniorb-list/2003-October/024392.html
>>
>>which clarifies some details.
>>
>
> To answer some of the questions raised by that, I should explain the
> purpose of the _OMNIORB_NTDLL_IMPORT macro. If you just build a DLL on
> Windows, no symbols at all are exported from it. The omniORB build
> process creates a .def file that causes (almost) everything to be
> exported from it.
>
> When using a DLL, exported functions are used automatically. However,
> exported static data is not. That is the purpose of the
> _OMNIORB_NTDLL_IMPORT macro. It marks those bits of static data that
> must be available to importers of the DLL.
>
> Cheers,
>
> Duncan.
>
More information about the omniORB-list
mailing list