You're right, Gerard. You need more stuff in the client classpath. Besides prepending jacorb.jar to the bootclasspath, I have the following jars in my clients' classpath: jboss-client.jar, jboss-common-client.jar, jboss-iiop-client.jar, jboss-j2ee.jar, and log4j.jar. All of these are in the directory $JBOSS_HOME/client.
Here is a command line that works for me: java -Xbootclasspath/p:$JBOSS_HOME/client/jacorb.jar -classpath \ .:$JBOSS_HOME/client/jboss-client.jar:$JBOSS_HOME/client/jboss-common-client.jar:$JBOSS_HOME/client/jboss-iiop-client.jar:$JBOSS_HOME/client/jboss-j2ee.jar:$JBOSS_HOME/client/log4j.jar \ -Djava.security.policy=/home/reverbel/java.policy.for-tests \ -Djava.security.manager MyClient The properties java.security.policy and java.security.manages properties enable stub downloading from the JBoss server. The java.policy file should grant permission for connecting to the port 8083 of the JBoss server. The client library will use HTTP to automatically download client stubs from the server. With this arrangement you do not need to do anything to generate client stubs in advance. An alternative arrangement is to generate client stub classes with `rmic -iiop' and put these classes in the client classpath. (This would be worthwhile for very short-lived clients, so that you don't have an extra HTTP request. For longer-lived clients the cost of the HTTP request should not be significant.) In this case you won't need the java.security.manager and the java.security.policy properties. From the stack trace below it seems you are now getting an exception after you've obtained the initial CosNaming context. This is certainly an improvement. However, the stack trace does not look like one caused by the lack of some jars in the client classpath, or by the lack of java.security properties. My guess is that you might be attempting to bind to a CosNaming context something that is not a reference to a CORBA object RMI/IIOP interface. But this is just a guess... Good luck, Francisco On Mon, 10 Jun 2002, Gerard BUNEL wrote: > Hi, > > I changed my command line to launch my application but still get Exception as > you can see belaw. > are there some extra jar or dir to put in the CLASSPATH ? > > How are loaded stubs ? In my previous configuration, using BEA, I've put all my > stubs in the classpath of the client application and also > in the classpath of the BEA server (because I use JSP that refer to RMI/IIOP > Objects) > Is this way correct for JBoss ? > > D:\Projets\CTI>java -Xbootclasspath/p:jacorb.jar;jboss-iiop-client.jar > -classpat > h classes;xerces.jar;;cryptix32.jar;gonative.jar;j2ee12.jar > com.ftrd.cti.server. > CTIServerImpl cti1.xml > ##################################################################### > WARNING: no properties file found! This warning can be ignored > for applets. A file file called "jacorb.properties" or > ".jacorb_properties" should be present in the classpath, > the home directory (C:\WINNT\Profiles\gbunel), the current directory (.) or > in Javas lib directory (D:\jdk1.3.1_01\jre) > ##################################################################### > > [ Property "jacorb.hashtable_class" not present. Will use default hashtable > impl > ementation ] > [ ConnectionManager: created new conn to target 192.9.200.27:8683 ] > [ No CodeSetComponentInfo present in IOR. Will use default CodeSets ] > [ Trying to connect to 192.9.200.27:8683 ] > [ Succeeded to connect to 192.9.200.27:8683 ] > javax.naming.ConfigurationException: Problem invoking > javax.rmi.CORBA.Stub.conne > ct(). Root exception is org.omg.CORBA.NO_IMPLEMENT: > at org.omg.CORBA.ORB.connect(ORB.java:128) > at com.ftrd.cti.publish._RMICTIServerPublisher_Tie.orb(Unknown Source) > at > com.sun.corba.se.internal.javax.rmi.CORBA.StubDelegateImpl.connect(St > ubDelegateImpl.java:215) > at javax.rmi.CORBA.Stub.connect(Stub.java:151) > at java.lang.reflect.Method.invoke(Native Method) > at > com.sun.jndi.toolkit.corba.CorbaUtils.remoteToCorba(CorbaUtils.java:1 > 11) > at > com.sun.jndi.cosnaming.RemoteToCorba.getStateToBind(RemoteToCorba.jav > a:64) > at > javax.naming.spi.NamingManager.getStateToBind(NamingManager.java:845) > > at com.sun.jndi.cosnaming.CNCtx.callBindOrRebind(CNCtx.java:458) > at com.sun.jndi.cosnaming.CNCtx.rebind(CNCtx.java:567) > at com.sun.jndi.cosnaming.CNCtx.rebind(CNCtx.java:584) > at javax.naming.InitialContext.rebind(InitialContext.java:366) > at com.ftrd.cti.server.CTIServerImpl.run(CTIServerImpl.java:2495) > at java.lang.Thread.run(Thread.java:484) > > Francisco Reverbel a écrit : > > > On Fri, 7 Jun 2002, Gerard BUNEL wrote: > > > > > Francisco Reverbel a écrit : > > > > > > > I have seen a stack trace like this before. Aren't you using an older > > > > JacORB version at the client side by any chance? > > > > > > > > > > Don't know. I downloaded the jboss-all which included the jacorb.jar. Is > > > there mean to know the version ? > > > > In case you have more than one jacorb.jar file in the client machine, > > you need to make sure that the right one is used. Put in the client > > classpath the jacorb.jar file provided with JBoss. Better yet, prepend > > it to the boot classpath, so you can be certain it will be seen before > > any other: > > > > java -Xbootclasspath/p:SOME_DIR/jacorb.jar ... YourClient > > > > If you are using some script provided with JacORB (jaco or jaco.bat) > > to start you client, change the script so that uses the right jar > > file. There will be an Xbootclasspath in the script, make it point > > to the jacorb.jar file provided with JBoss. > > > > Let me know if this works or not. > > > > Best, > > > > Francisco > > > > _______________________________________________________________ > > > > Don't miss the 2002 Sprint PCS Application Developer's Conference > > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > -- > [EMAIL PROTECTED] - Atlantide - http://www.ago.fr/atlantide/ > Technopole Brest Iroise BP 80802 - Site du Vernis - 29608 Brest cedex - France > Tel. : +33 2 98 05 43 21 - Fax. : +33 2 98 05 20 34 > e- _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
