I have looked at a number of ejb deployments and they don't show this issue. Something is wrong with the ejb-ref link or the context listing for this deployment. Can you post the ear to sourceforge so I can look at it?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx Subject: Problem with JNDI binding of EJB componets... perhaps Date: Thu, 9 May 2002 11:08:03 -0700 From: Jason Dillon <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Ola. I in the middle of migrating my app from a pre-3.0 to 3.0 and I happened to run into a bit of oddness with JNDIView. Could be that I have something messed up, but I can't tell really. I have a set of EJB deployables that seem to deploy fine, but if I JNDIView.list() I get some ClassCastExceptions. I added a bit of logging to the loop where it displays the tree. From the logs it looks like the pair's for the bean homes show a different type than the value which is actually returned. Because the NameClassPair has the wrong class type JNDIView barfs because it expects a LinkRef and not a Reference: <snip> 2002-05-09 11:05:47,702 DEBUG [org.jboss.naming.JNDIView] pair: SequenceManagerHome: javax.naming.LinkRef 2002-05-09 11:05:47,703 DEBUG [org.jboss.naming.JNDIView] type: class javax.naming.LinkRef 2002-05-09 11:05:47,703 DEBUG [org.jboss.naming.JNDIView] looking up LinkRef; name=SequenceManagerHome 2002-05-09 11:05:47,704 DEBUG [org.jboss.naming.JNDIView] Object type: class javax.naming.Reference 2002-05-09 11:05:47,704 ERROR [org.jboss.naming.JNDIView] Invalid LinkRef java.lang.ClassCastException: javax.naming.Reference at org.jboss.naming.JNDIView.list(JNDIView.java:400) at org.jboss.naming.JNDIView.list(JNDIView.java:446) at org.jboss.naming.JNDIView.list(JNDIView.java:446) at org.jboss.naming.JNDIView.list(JNDIView.java:125) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl . java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat c her.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at com.sun.jdmk.comm.HtmlInvokePage.buildPage(HtmlInvokePage.java:240) at com.sun.jdmk.comm.HtmlRequestHandler.processGetRequest(HtmlRequestHandler.ja v a:325) at com.sun.jdmk.comm.HtmlRequestHandler.processRequest(HtmlRequestHandler.java: 1 52) at com.sun.jdmk.comm.HtmlRequestHandler.doRun(HtmlRequestHandler.java:79) at com.sun.jdmk.comm.ClientHandler.run(ClientHandler.java:84) at java.lang.Thread.run(Thread.java:536) </snip> Any idea why this is happening? --jason ------------------------------------------------------- _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
