We get this identical problem using weblogic with Tomcat 3.1. The 'solution' is to put the interface you're casting to in the tomcat/lib directory, not in your WEB-INF/lib directory. Tomcat3.1 had a classloader bug which meant that classes loaded from tomcat/lib could not see classes loaded from WEB-INF/lib, which caused this sort of problem. I've heard that it's fixed in 3.2beta4 and 4m1, but I haven't checked them out yet. Tom Kevin Lewis writes: > In August, Werner Ramaekers reported a problem exactly like I'm having > now. > > When I do a PortableRemoteObject.narrow from Tomcat (using the > TomcatService), I get a class cast. > > The object I'm casting is the result of a JNDI lookup. It reports to be > of type "$Proxy7", but implements the interface to which I am casting (I > printed them out), so I'm thinking the lookup is correct. > > Does anyone know what I am doing wrong to get this problem? > > Thanks! > > (Here's a bit of the stack trace.) > > java.lang.ClassCastException > at > com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(Unknown > Source) > at javax.rmi.PortableRemoteObject.narrow(Unknown Source) > > -- > Kevin Lewis > Middle Reliever > Axys Solutions > http://www.AxysSolutions.com/ > > > -- > -------------------------------------------------------------- > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] > Problems?: [EMAIL PROTECTED] > -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
