[omniORB] URGENT REQUEST FOR HELP omniORB version 3 omniidl location

[dominic]

Hi All,

We have an urgent requirement to update some stub files using omniidl but cannot find this anywhere on the UNIX platform. Could you let us know where to fin the executable as we need to make changes ASAP

Regards
Dominic

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060816/7cdca330/attachment.htm

[dominic]

I should state that we have found several directories called omniidl but not an executable file anywhere? Any idea how we can make a new omniidl compiler (I believe this is actually a python script file on UNIX)



________________________________

From: Roman Neuhauser [mailto:***@sigpipe.cz]
Sent: Wed 16/08/2006 18:08
To: dominic
Cc: omniorb-***@omniorb-support.com
Subject: Re: [omniORB] URGENT REQUEST FOR HELP omniORB version 3 omniidl location

Post by dominic
We have an urgent requirement to update some stub files using omniidl
but cannot find this anywhere on the UNIX platform.

Try putting the following line in the shell prompt of your "UNIX
platform":

find / -iname \*omni\*

--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060816/f8c0f8dd/attachment.htm

[Alex Tingle]

omniidl is actually implemented as a C++ Python module. You need to
build and install the omniORB project. Provided your Unix platform is
supported it's fairly easy. Just download the tarball and follow the
instructions in README.unix.

The short version is...

$ cd $OMNIORB_TOP
$ mkdir build
$ cd build
$ ../configure [configure options]
$ make
$ su -
# make install

Once you've done that, you should just be able to run omniidl from the
command line.

-Alex

--
:: Let me solve your problems: http://www.firetree.net/consulting/
:: alex.tingle AT firetree.net [phone]

Post by dominic
I should state that we have found several directories called omniidl
but
not an executable file anywhere? Any idea how we can make a new
omniidl
compiler (I believe this is actually a python script file on UNIX)
_____
Sent: Wed 16/08/2006 18:08
To: dominic
Subject: Re: [omniORB] URGENT REQUEST FOR HELP omniORB version 3
omniidl
location

Post by dominic
We have an urgent requirement to update some stub files using omniidl
but cannot find this anywhere on the UNIX platform.

Try putting the following line in the shell prompt of your "UNIX
find / -iname \*omni\*
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
<http://bash.org/?255991>
_______________________________________________
omniORB-list mailing list
http://www.omniorb-support.com/mailman/listinfo/omniorb-list

[dominic]

Hi Alex,

I have used the windows omniidl to create the stubs, then transfered these to UNIX and used them to recompile the shared objects on both servers but we are getting an error when running the perl module which calls the CORBA object the process is as follows.

1. Perl Module calls compiled Perl Library
2. Library makes call to compiled C++ .so object on server 1
3. .so object on server 1 calls method via CORBA on server 2
4. .so object on server 2 calls method in JAR file which updates an Oracle database wth the data passed to it on server 2.

2 questions

1. How can we trace what is happening within the omniORB call across the servers, we are putting printf statements in the C++ but not seeing any output.
2. Can you compile the stubs on windows and transfer these to UNIX (they look ok from a visual point of view when comparing to old stub files.

Regards
Dominic


________________________________

From: Alex Tingle [mailto:***@bronermetals.com]
Sent: Wed 16/08/2006 17:13
To: Users omniORB; dominic
Subject: Re: [omniORB] URGENT REQUEST FOR HELP omniORB version 3 omniidl location



omniidl is actually implemented as a C++ Python module. You need to
build and install the omniORB project. Provided your Unix platform is
supported it's fairly easy. Just download the tarball and follow the
instructions in README.unix.

The short version is...

$ cd $OMNIORB_TOP
$ mkdir build
$ cd build
$ ../configure [configure options]
$ make
$ su -
# make install

Once you've done that, you should just be able to run omniidl from the
command line.

-Alex

--
:: Let me solve your problems: http://www.firetree.net/consulting/
:: alex.tingle AT firetree.net [phone]

Post by dominic
I should state that we have found several directories called omniidl
but
not an executable file anywhere? Any idea how we can make a new
omniidl
compiler (I believe this is actually a python script file on UNIX)
_____
Sent: Wed 16/08/2006 18:08
To: dominic
Subject: Re: [omniORB] URGENT REQUEST FOR HELP omniORB version 3
omniidl
location

Post by dominic
We have an urgent requirement to update some stub files using omniidl
but cannot find this anywhere on the UNIX platform.

Try putting the following line in the shell prompt of your "UNIX
find / -iname \*omni\*
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
<http://bash.org/?255991>
_______________________________________________
omniORB-list mailing list
http://www.omniorb-support.com/mailman/listinfo/omniorb-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20060817/b1062e2c/attachment.htm

[Sean Parker]

Hello -

Two questions...

1) is there a way to redirect the trace's (ie. traceLevel
40) besides shell-stdout-redirect or remapping/duping
stdout?... to a FILE* or some other stream mechanism -
preferably a callback function*. It would be nice to
1) worst case, pump traces to a file independent of
stdout/err so that I have that data only
2) better case: 1) above with time stamps, and logging
some user-defined context strings
3) best case: be able to give a callback function
ptr so I can do my own data insertion; before
putting it in a file, for example.

I looked in the src and it didn't seem trivial to modify
it... This would facilitate better network traffic analysis
within the context of certain application actions. I'm the
only one using CORBA in our company, and it'd be nice to be
able to make direct functional comparisons - atleast using
OmniORB as a benchmark.


2) Are there other under-the-cover optimizations that could
be exploited to improve performance? For example, the
manual suggests turning of the [thread] Context option.
It'd be nice to also be able to compile-out assertions,
other ptr checks, etc. If I get the system running really
well, I'd like to be able to go back and reduce as much
overhead as possible...


Thanks
Sean

Post by Alex Tingle
omniidl is actually implemented as a C++ Python module.
You need to
build and install the omniORB project. Provided your Unix
platform is
supported it's fairly easy. Just download the tarball and
follow the
instructions in README.unix.
The short version is...
$ cd $OMNIORB_TOP
$ mkdir build
$ cd build
$ ../configure [configure options]
$ make
$ su -
# make install
Once you've done that, you should just be able to run
omniidl from the
command line.
-Alex
--
http://www.firetree.net/consulting/
:: alex.tingle AT firetree.net [phone]

Post by dominic
I should state that we have found several directories

called omniidl

Post by dominic
but
not an executable file anywhere? Any idea how we can

make a new

Post by dominic
omniidl
compiler (I believe this is actually a python script

file on UNIX)

Post by dominic
_____
Sent: Wed 16/08/2006 18:08
To: dominic
Subject: Re: [omniORB] URGENT REQUEST FOR HELP omniORB

version 3

Post by dominic
omniidl
location

Post by dominic
We have an urgent requirement to update some stub

files using omniidl

Post by dominic

Post by dominic
but cannot find this anywhere on the UNIX platform.

Try putting the following line in the shell prompt

of your "UNIX

Post by dominic
find / -iname \*omni\*
--
How many Vietnam vets does it take to screw in a light

bulb?

Post by dominic
You don't know, man. You don't KNOW.
Cause you weren't THERE.

http://bash.org/?255991

Post by dominic
<http://bash.org/?255991>
_______________________________________________
omniORB-list mailing list

http://www.omniorb-support.com/mailman/listinfo/omniorb-list

Post by Alex Tingle
_______________________________________________
omniORB-list mailing list

http://www.omniorb-support.com/mailman/listinfo/omniorb-list
God Bless
Sean Parker




__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Duncan Grisby]

Post by Sean Parker
1) is there a way to redirect the trace's (ie. traceLevel
40) besides shell-stdout-redirect or remapping/duping
stdout?... to a FILE* or some other stream mechanism -
preferably a callback function*. It would be nice to

omniORB::setLogFunction does what you want:

http://omniorb.sourceforge.net/omni40/omniORB/omniORB004.html#htoc51

Post by Sean Parker
2) Are there other under-the-cover optimizations that could
be exploited to improve performance? For example, the
manual suggests turning of the [thread] Context option.
It'd be nice to also be able to compile-out assertions,
other ptr checks, etc. If I get the system running really
well, I'd like to be able to go back and reduce as much
overhead as possible...

You can easily turn off the assertions by changing the definition in
include/omniORB4/omniInternal.h. I don't think it makes much difference,
though. There aren't really any other things you can disable.

Cheers,

Duncan.