RE: [JBoss-user] Narrowing problems with tomcat and jboss 2.2.1

[J�rg Schorr]

Title: Narrowing problems with tomcat and jboss 2.2.1

Ok solved the problem. Finally found what I needed in chapter 11 of the documentation http://www.jboss.org/documentation/HTML/ch11.html#howtotomcat

 

jorg 

-----Original Message-----
From: J�rg Schorr
Sent: Tuesday, June 05, 2001 9:13 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] Narrowing problems with tomcat and jboss 2.2.1

Thanks for the answer, but this does not solve my problem, as I have a ClassNotFoundException. Actually I must admit that my message was misleading. The real problem happens at the lookup (based on the ClassNotFoundException).

Did something changed for the classpath for the embedded tomcat in jboss 2.2.1?

 

Thanks,

jorg

-----Original Message-----
From: Jim Brownfield [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 03, 2001 5:39 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Narrowing problems with tomcat and jboss 2.2.1

Someone correct me if I'm wrong, but I believe there are three solutions possible:

 

1)  Upgrade to the 1.3 JVM which includes the RMI-IIOP

 

2)  Install Sun's 1.2 add-on RMI-IIOP installation (you can only do this if you're running on Windows or Solaris, the package doesn't exist for other installations).

 

3)  Just don't narrow the object reference (this is what I had to do).  Just cast the jndi lookup directly to the home interface.  This is not "technically" correct as EJB 1.1 specs require the narrowing, but it seems to work.

 

Good luck!

Jim

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of J�rg Schorr
Sent: Sunday, June 03, 2001 1:05 AM
To: '[EMAIL PROTECTED]'
Subject: [JBoss-user] Narrowing problems with tomcat and jboss 2.2.1

Hi,

we are moving to jboss 2.2.1 (with embedded tomcat 3.2) and are facing narrowing problems (with a ClassNotFoundException of my EJB as root exception) we did not have with jboss 2.0 FINAL.

I saw on this list that someone 'solved' the problem by putting his jar file in the lib/ext directory. But I cannot imagine that this is the solution, especially because of the hot deployment feature.

I am sure it is 'simply' a configuration problem, but we couldn't figure it out until now by looking at the migration 2.0 -> 2.2.1 documentation.

Any help is welcome, thanks,
jorg