[mico-devel] mico gcc4.1 and VC2005 issue of sequence of valuetype
Hi, karel I am stuck with the issue I reported to u earlier. I have been working on resolving this issue for last 14 days but no success. Please help me out PROBLEM STATEMENT: i have the java server based on spring framework which exposes its been called SessionService on iiop and registered it on jac naming service. The client is developed on Visual studio 2005 using mico orb “mico-cl8-10.4.06” (special build by soran for vc2005 ) version which i complied on VS2005. I have an valuetype seq1_ Session which is an sequence of Session valuetype corresponding to this value type I have factory registered with orb to construct this on client side. Problem I face is when I make a call Get AllSession() on SessionService which returns the seq1_session The call is successful , I get the se1_session. I iterate over the seq1_session and get the session valuetype Up to this every thing work fine but when I try to dynamically cast the session value type to session_impl (which is a wrapper over the OBV session class ) The dynamic_cast fail it return me the NULL. But if I use the typeid to check the object type on session it gives me the session_impl I have debug the mico code and what is found is seq1_session demarshalling is proper. I can sess the session valuetype properly get constructed and the data is properly Filled in the session valuetype. I get the properly build sequence. But not able to understand the why I am not able to dynamic_cast it to session_impl when the object it created at the time of demashal is session_impl in the call create_for_unmarshal in session factory. It is very strange that if i compile the client on VC7/Visual Studios 2002 then the same code works using the mico build 2.3.12 compiled on vc7 And Also on Gcc 401 version I get the same problem. The dynamic_cast fails. In all these cases above no change has been made in the Java Server. Please help me out to solve the issue. I can provide u the sample code. --Regards Guminder Singh Member (SDG) Core Technologies Group Quark Media House pvt Ltd. A- 45 industrial Area (Mohali) Phone: 91 -172-2299440 [EMAIL PROTECTED] CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone xxx.xxx. or return e-mail message [EMAIL PROTECTED] and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
[mico-devel] Re: oh dear.. should mico/demo werk? is mico broke?
On Tue, 10 Oct 2006, KAYVEN RIESE wrote: -o client c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c server .cc -o server.o c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -L../../../ libs tree.o tree_impl.o server.o -lmico2.3.12 -lcompat -lssl -lcrypto -lm -lp thread -o server gmake[2]: Leaving directory `/usr/local/mico/demo/obv/tree' gmake[2]: Entering directory `/usr/local/mico/demo/obv/tricky' echo '# Module dependencies' > .depend /usr/local/mico/./admin/mkdepend -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE *.c *.cc >> .depend /usr/local/mico/./idl/idl tricky.idl c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c tricky .cc -o tricky.o c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c tricky _impl.cc -o tricky_impl.o c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c client .cc -o client.o c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -L../../../ libs tricky.o tricky_impl.o client.o -lmico2.3.12 -lcompat -lssl -lcrypto -lm -lpthread -o client c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c server .cc -o server.o c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -L../../../ libs tricky.o tricky_impl.o server.o -lmico2.3.12 -lcompat -lssl -lcrypto -lm -lpthread -o server gmake[2]: Leaving directory `/usr/local/mico/demo/obv/tricky' gmake[1]: Leaving directory `/usr/local/mico/demo/obv' gmake[1]: Entering directory `/usr/local/mico/demo/services' Makefile:52: warning: overriding commands for target `install' ../MakeVars:76: warning: ignoring old commands for target `install' for i in naming naming-lb naming-mt events property-daemon; do gmake -C $i || e xit 1; done gmake[2]: Entering directory `/usr/local/mico/demo/services/naming' echo '# Module dependencies' > .depend /usr/local/mico/./admin/mkdepend -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE *.c *.cc >> .depend /usr/local/mico/./idl/idl account.idl c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c accou nt.cc -o account.o c++ -I. -I../../../include -O2 -Wall -D_REENTRANT -D_THREAD_SAFE -c clien t.cc -o client.o client.cc:2:28: coss/CosNaming.h: No such file or directory client.cc: In function `int main(int, char**)': client.cc:27: error: `CosNaming' has not been declared client.cc:27: error: `NamingContext_var' undeclared (first use this function) client.cc:27: error: (Each undeclared identifier is reported only once for each function it appears in.) client.cc:27: error: expected `;' before "nc" client.cc:30: error: `nc' undeclared (first use this function) client.cc:39: error: `CosNaming' has not been declared client.cc:39: error: `Name' undeclared (first use this function) client.cc:39: error: expected `;' before "name" client.cc:40: error: `name' undeclared (first use this function) client.cc:56: error: `CosNaming' has not been declared client.cc:56: error: `NotFound' has not been declared client.cc:56: error: invalid catch parameter client.cc:60: error: `CosNaming' has not been declared client.cc:60: error: `CannotProceed' has not been declared client.cc:60: error: invalid catch parameter client.cc:64: error: `CosNaming' has not been declared client.cc:64: error: `InvalidName' has not been declared client.cc:64: error: invalid catch parameter client.cc:56: error: `...' handler must be the last handler for its try block client.cc:60: error: `...' handler must be the last handler for its try block gmake[2]: *** [client.o] Error 1 gmake[2]: Leaving directory `/usr/local/mico/demo/services/naming' gmake[1]: *** [subs] Error 1 gmake[1]: Leaving directory `/usr/local/mico/demo/services' gmake: *** [prg] Error 1 bsd# pwd /usr/local/mico/demo bsd# ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] Building mico on Cygwin
Hi! I experienced the same linking problem, but I solved it by adding the lib "crypto" (and maybe "ssl") somewhere in the Makefile. Search for gcc's "-l" parameter inside the Makefile (maybe more than a single one). Seems that libssl depends on libcrypto which does not get linked via the make procedure. After building MICO you always have to link libcrypto/libssl to your MICO-based projects. -Patrick ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
[mico-devel] Building mico on Cygwin
I am trying to build "mico" under Cygwin. I have read INSTALL.txt and have installed the tools (gcc) as well as openssl package. Still, I get the following errors while building - ../libs/libmico2.3.12.a(ssl.o):ssl.cc:(.text+0x53db): undefined reference to `_BIO_ctrl' ../libs/libmico2.3.12.a(ssl.o):ssl.cc:(.text+0x53e8): undefined reference to `_SSL_new' ../libs/libmico2.3.12.a(ssl.o):ssl.cc:(.text+0x5407): undefined reference to `_SSL_set_bio' ../libs/libmico2.3.12.a(ssl.o):ssl.cc:(.text+0x57f6): undefined reference to `_SSL_accept' ../libs/libmico2.3.12.a(ssl.o):ssl.cc:(.text+0x5ac5): undefined reference to `_SSL_set_connect_state' in /lib, I have [mico$:551] ls /lib/*ssl* /lib/libgnutls-openssl.dll.a /lib/libssl.a /lib/libgnutls-openssl.la /lib/libssl.dll.a [mico$:552] What am I missing? Seemed to have created most of the object files without problems. Thx Arun ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] Re: installation of mico failed
Hi, We've had exactly the same issue with hosts files, both on the server (Redhat) and the client (Windows) although the client is using TAO. Now that we know the solution it's not a big problem! But why does MICO have to know the hostname? It seems quite unnecessary. What is wrong with just having the IP address(es)? I consider this to be a bug!! Having the correct IP Addresses in the hosts file on both the client and server is just a fairly easy workaround. Your thoughts? Is there a good reason for this, something which could be fixed in a future release? Chris On 10/10/06, Andrew Zinn <[EMAIL PROTECTED]> wrote: This is something that would be useful in the INSTALL.txt documentation. I just helped a friend install MICO on a Fedora Core 5 machine. I knew he had to edit his hosts file, but it wasn't obvious to him. Thanks for all the work put into MICO. Since I haven't seen it listed, I'll let you know I have MICO working with Linux 2.6 on x86_64 machines. Andrew Zinn >From: Karel Gardas <[EMAIL PROTECTED]> > > >don't focus your attention solely on DNS configuration. In fact I would >rather recommend you to inspect your /etc/hosts file which Rudolf already >suggested. The whole issue is that your machine of some name needs to be >able to also get it's own IP address and to the machine IP you need to be >able to get the machine name. For both these tasks /etc/hosts is perfectly >enough, you just need to setup or even install your machine correctly. ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] Re: installation of mico failed
This is something that would be useful in the INSTALL.txt documentation. I just helped a friend install MICO on a Fedora Core 5 machine. I knew he had to edit his hosts file, but it wasn't obvious to him. Thanks for all the work put into MICO. Since I haven't seen it listed, I'll let you know I have MICO working with Linux 2.6 on x86_64 machines. Andrew Zinn From: Karel Gardas <[EMAIL PROTECTED]> To: KAYVEN RIESE <[EMAIL PROTECTED]> CC: mico-devel@mico.org, [EMAIL PROTECTED] Subject: Re: [mico-devel] Re: installation of mico failed Date: Sat, 23 Sep 2006 13:36:28 +0200 (CEST) Hi, don't focus your attention solely on DNS configuration. In fact I would rather recommend you to inspect your /etc/hosts file which Rudolf already suggested. The whole issue is that your machine of some name needs to be able to also get it's own IP address and to the machine IP you need to be able to get the machine name. For both these tasks /etc/hosts is perfectly enough, you just need to setup or even install your machine correctly. BTW: What you get if you execute this command-line: ping `hostname` is ping able to ping your host IP address? 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 Fri, 22 Sep 2006, KAYVEN RIESE wrote: kayve# cat /etc/resolv.conf nameserver 192.168.0.1 kayve# http://192.168.0.1/modeminfo.htm is an SBC web page (that's my DSL provider) it has this info on it DSL UP Connection UP User ID [EMAIL PROTECTED] Connected at3008 Kbps (downstream) 512 Kbps (upstream) IP Address 68.127.180.94 IP Gateway 151.164.184.80 DNS Servers 68.94.156.1 dnsr1.sbcglobal.net 68.94.157.1 dnsr2.sbcglobal.net ModePPP on the modem (Public IP for LAN device) Timeout Never Modem Information Modem Name SpeedStream Model 4100 Serial Number 20013A31BBF13 Software Version1.0.0.48 MAC Address 00:13:A3:1B:BF:13 First Use Date 2005/09/17 00:31:49 GMT Local Network Modem IP Address192.168.0.1 Ethernet Status Connected On Sat, 23 Sep 2006, Rudolf Schreiner wrote: On Fri, 22 Sep 2006, KAYVEN RIESE wrote: okay, no advice on this? kayve# uname -a FreeBSD kayve.domain_not_set.invalid 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun This doesn't look good. MICO requires a correct network installation. man rc.conf man hosts man named man sysinstall ... All you need is a standard FreeBSD installation with networking configured. And then the standard MICO works out of the box. Cheers, Rudi ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel -- Karel Gardas [EMAIL PROTECTED] ObjectSecurity Ltd. http://www.objectsecurity.com ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] thought i could make
On Tue, 10 Oct 2006, KAYVEN RIESE wrote: i need to do the idl compile step first? i guess i need to buy my mico textbook now. i can't view powerpoints while running my freeBSD my root prompt is "bsd#" Using root account for compilation is not recommended practise. just trying to compile a test, demo/generic ? should i be able to make it or not? run: run_test clean: rm -f *.o *.ior core client server *~ .depend bsd# make server You need to make sure you use GNU Make, on BSD you should usually use `gmake' command. Cheers, Karel -- Karel Gardas [EMAIL PROTECTED] ObjectSecurity Ltd. http://www.objectsecurity.com ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
[mico-devel] thought i could make
i need to do the idl compile step first? i guess i need to buy my mico textbook now. i can't view powerpoints while running my freeBSD my root prompt is "bsd#" just trying to compile a test, demo/generic ? should i be able to make it or not? run: run_test clean: rm -f *.o *.ior core client server *~ .depend bsd# make server "../../MakeVars", line 142: Missing dependency operator "../../MakeVars", line 150: Need an operator "../../MakeVars", line 153: Need an operator "../../MakeVars", line 155: Missing dependency operator "../../MakeVars", line 158: Need an operator "../../MakeVars", line 161: Need an operator "../../MakeVars", line 169: Missing dependency operator "../../MakeVars", line 170: Missing dependency operator "../../MakeVars", line 178: Need an operator "../../MakeVars", line 179: Need an operator "../../MakeVars", line 207: warning: duplicate script for target "%.cc" ignored "../../MakeVars", line 208: warning: duplicate script for target "%.cc" ignored "../../MakeVars", line 238: warning: duplicate script for target "%.ps" ignored "../../MakeVars", line 244: warning: duplicate script for target "%.moc" ignored "../MakeVars", line 43: Missing dependency operator "../MakeVars", line 45: Need an operator "../MakeVars", line 47: Need an operator "../MakeVars", line 51: Missing dependency operator "../MakeVars", line 53: Need an operator "../MakeVars", line 55: Need an operator "../MakeVars", line 60: Missing dependency operator "../MakeVars", line 62: Need an operator "../MakeVars", line 64: Need an operator "../MakeVars", line 69: Missing dependency operator "../MakeVars", line 71: Need an operator "../MakeVars", line 73: Need an operator "../MakeVars", line 86: Missing dependency operator "../MakeVars", line 87: Could not find .depend "../MakeVars", line 88: Need an operator make: fatal errors encountered -- cannot continue bsd# pwd /usr/local/mico/demo/generic bsd# ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
