Well, as it turns out it was a "jar" problem. I had a servlet that created the cache, started it and inserted the TreeCache object in JNDI. I made sure that this servlet always ran first (in WebLogic). The war file had the jboss-cache related jars in its WEB-INF/lib dir
My ear's also had the jboss-cache related jars in its APP-INF/lib dir. However the JNDI (in WebLogic) would not allow a TreeCache object inserted by the servlet to be cast to a TreeCache object for the EJB because of the two seperate jars. I therefore took them out of the war and ear files and put them in the (WebLogic) server's path. All seems hunky dory now. Strange JNDI behaviour, but I suspect this is a WebLogic rather than a JNDI issue per se. Cheers -raj View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3906264#3906264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3906264 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
