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
obtained a reference to the CosNaming service and got an exception when
attempting to register (rebind) an object with it. Is this correct?
If so, what kind of object are you attempting to register with the
CosNaming service? Is it a CORBA object? Please make sure that
(obj instanceof org.omg.CORBA.Object)
evaluates to true. In case it does, please check if you can successfully
call
orb.object_to_string(obj);
where orb refers to JacORB. If this succeeds, then a call like
cosNamingCtx.rebind(name, obj)
should also succeed.
The org.omg.CORBA.ORB.connect() call in your stack trace is not
supported by JacORB. It has been deprecated by the OMG in favor of the
POA-based API. Its presence suggests that you are passing to rebind()
(1) either an object that is not a CORBA object at all (and the Sun
JNDI provider is attempting to convert it into a CORBA object
with a connect() call on the Sun ORB)
(2) or it is a CORBA object implemented with the old BOA-based model,
which is not supported by JacORB. If this is the case, a call like
jacorb.object_to_string(obj) should fail.
A final thing: Why do you want to register a object of yours with the
JBoss CosNaming service? The JBoss server uses this service to make
EJBHome references available to RMI/IIOP or CORBA clients. I would not
expect clients to register their own objects with JBoss CosNaming, but
just to perform EJBHome lookups on it. I have actually considered
disallowing clients to perform any write operations to the CosNaming
context in which EJBHomes are registered (this has been in my TODO list
for a while), so that a rogue client cannot erase or overwrite EJBHome
bindings (this is possible today).
Maybe JBoss should provide two distinct CosNaming roots to its clients:
a read-only context, in which clients would look for EJBHomes, and a
context in which clients could register their own objects. This should
not be hard to do.
Regards,
Francisco
On Fri, 14 Jun 2002, Gerard BUNEL wrote:
> 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 JacORB NameService when I
>try to bind in it. It seems, that Sun IIOP level uses a CodeSet
> not supported by JacORB. I've tried the same with an ORBacus Naming Service and it
>works fine.
>
> So is it a bug or a lack of feature in JacORB, or is it, somewhere, a missing
>configuration option ?
>
> ############################ StackTrace ############################
> org.omg.CORBA.MARSHAL: The char type only allows single-byte codesets, but the s
> elected one is: Unknown TCS: 10020
> at org.jacorb.orb.CDRInputStream.read_string(CDRInputStream.java:627)
> at org.jacorb.orb.ServantDelegate._invoke(ServantDelegate.java:305)
> at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java
> :232)
> at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:456)
> at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:581)
>
> Now if I try using JacORB on the client side (by using the
>-Xbootclasspath/p:jacorb.jar and an orb.properties)
> I get the following, well know (from my previous mail) exception:
>
> D:\Projets\CTI>java -Xbootclasspath/p:jacorb.jar -classpath classes;xerces.jar;c
> ryptix32.jar;gonative.jar;j2ee12.jar com.ftrd.cti.server.CTIServerImpl cti2.xml
>
> JacORB V 1.4 beta 4, www.jacorb.org
> (C) Gerald Brose, FU Berlin, March 2002
> [ Trying to connect to 192.9.200.27:4585 ]
> 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:2489)
> at java.lang.Thread.run(Thread.java:484)
> JacORB V 1.4 beta 4, www.jacorb.org
> (C) Gerald Brose, FU Berlin, March 2002
>
> I've searched the JacORB mailing-list archives and found nothing about this.
> Any other IDEA ?
>
>
> --
> [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-mail: [EMAIL PROTECTED]
> Centre Affaires Oberthur - 74D, rue de Paris - 35700 Rennes - France
> Tel. : +33 2 99 84 15 84 - Fax : +33 2 99 84 15 85
> e-mail: [EMAIL PROTECTED]
>
>
>
_______________________________________________________________
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
