[JBoss-dev] [IIOP on JBoss] - Re: Problem calling EJB using RMI/IIOP while providing IOR f

[alan_burton]

Afraid not. We moved to a web services architecture which meant we no longer had a 
requirement to invoke the remote EJB using RMI/IIOP.

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3848730#3848730

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3848730


---
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] [IIOP on JBoss] - Problem calling EJB using RMI/IIOP while providing IOR for N

[alan_burton]

I'm trying to call a remote EJB deployed on JBoss 3.2.4 using RMI/IIOP. I reviewed the 
article located at http://www.jboss.org/developers/projects/jboss/IIOP. I was 
successful in calling the EJB using both corbaloc and IOR for the provider url when my 
client is compiled and run using JDK 1.4.2_04. However, when I use the IOR reference 
for the Corba Naming Service and compile and run my client using JDK 1.3.1_12 I get an 
org.omg.CORBA.INV_OBJREF exception. 

org.omg.CORBA.INV_OBJREF:   minor code: 1398079490  completed: No
at com.sun.corba.se.internal.core.CodeSetComponentInfo.read(CodeSetCompo
nentInfo.java:90)
at com.sun.corba.se.internal.core.Profile.(Profile.java:109)
at com.sun.corba.se.internal.core.IOR.getProfile(IOR.java:273)
at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(CDRInputStr
eam.java:590)
at com.sun.corba.se.internal.iiop.CDRInputStream.read_Object(CDRInputStr
eam.java:576)
at com.sun.corba.se.internal.corba.ORB.string_to_object(ORB.java:1079)
at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:274)
at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:213)
at com.sun.jndi.cosnaming.CNCtx.(CNCtx.java:68)
at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.ja
va:30)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
60)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241
)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.(InitialContext.java:193)
at com.eircom.ea.EAAccess.testNeon(EAAccess.java:180)
at com.eircom.ea.EAClient.main(EAClient.java:136)

I am tied to using the JDK 1.3.x as I am calling the EJB from within a java stored 
procedure on an Oracle 9.2 database. I don't want to use RMI/JRMP as this requires the 
JBoss client jars to be loaded into the database. I believe there is a known bug with 
JDK 1.3.x concerning code set negotiations. The article referenced above seems to 
indicate that it is possible to have IIOP clients access beans remotely deployed on 
JBoss using the Naming service IOR. Does anyone have any additional information that 
might help me resolve this issue or a workaround for the problem? 

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842050#3842050

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842050


---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development