Bugs item #643673, was opened at 2002-11-25 09:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=643673&group_id=22866
Category: JBossServer Group: None >Status: Closed Resolution: Invalid Priority: 5 Submitted By: Alvaro Mota Goncalves (alvaromota) Assigned to: Nobody/Anonymous (nobody) Summary: ClassCastException Initial Comment: SO - Linux RedHat JVM 1.3.1-06 Sun , 1.3.1 - Blackdown , 1.4.1 Sun JBOSS Server 3.0.4 and 3.0.3 A session Bean packaged in a jar file (Session01.jar) is calling one entity bean packaged in another jar file (Entity01.jar) . Works great. I have one client in Tomcat in another machine. If I hot-deploy Session01.jar, it's work. But hot-deploy Entity01 get 20:34:59,449 ERROR [LogInterceptor] RuntimeException: java.lang.ClassCastException: $Proxy156 at com.da.motion.testeAlvaro.model.statelessEJB.SManterTesteEJB.find All(SManterTes teEJB.java:75) The solution is to hot-deploy Entity01 and Session01 in sequence works fine. Thanks Alvaro ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2002-11-25 11:42 Message: Logged In: YES user_id=175228 All that says is that the $Proxy156 does not implement the interface the proxy is being cast to. This is expected if you redeploy the entity bean and perform a finder call from the session bean that has an explicit reference to the previous version of the entity interface. Unless there is an example that shows the session bean has no explicit references to the entity interfaces the redeployment described is not valid. ---------------------------------------------------------------------- Comment By: Bill Burke (patriot1burke) Date: 2002-11-25 11:32 Message: Logged In: YES user_id=176497 Re-opening. Look at the stack trace. The CCE is around $Proxy156. Is there something going on between UCL and dynamically generated classes via java.lang.reflect.Proxy? ---------------------------------------------------------------------- Comment By: Scott M Stark (starksm) Date: 2002-11-25 10:26 Message: Logged In: YES user_id=175228 Deployments with explicit references to each other must be deployed as a unit so that the Java type system remains consistent. The type of a class is its fully qualified name + the class loader that loaded it. You cannot arbitrary redeploy components and introduce a new type and expect previously deployed components to continue to work unless the interaction between the components is completely stateless with respect to the classes shared between deployments. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=643673&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
