Hello Gerard,
Right now I would suggest you to use JacORB at both sides, so we can
weed out any chance of ORB interoperability problems. Please use at
the client side the jacorb.jar file in the JBoss 3.0 distribution.
>From the stack trace below (the second one) I see that you have already
obt
Hello Francisco,
I've tried hard to find where was my problem but still not found any solution.
I've tested many configurations: using jacorb or not on client side, using a simple
COSNaming without JBoss to try to isolate the problem.
And that's the point I am: Below is the stack trace from JacO
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 dire
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
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
Oh, are trying to use a foreign key as a primary key? If you are, it is
not supported yet. A new guy Ken is working on this, and said it
"shouldn't be that hard" (that is what I said about the CMP 2.0 engine
when I started). If he has any luck, we should have this within a month
or two.
-d
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 ?
>
> JBoss requires JacORB 1.4. N
I have seen a stack trace like this before. Aren't you using an older
JacORB version at the client side by any chance?
JBoss requires JacORB 1.4. Neither JacORB 1.3.X or 1.4.betaX will work.
JacORB 1.4 was not yet publicly available when we released JBoss 3.0,
which went out with an unofficial
Helo,
Still trying to use RMI/IIOP with JBoss, and still not working.
I've forced my client app to use jacorb by setting properties this way:
Properties p = new Properties();
p.put ("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");
p.put( "org.omg.CORBA.ORBSingletonClass",
"org.jacor