I have two seam applications that are deployed in the same JBoss server. Those two EAR files share a common EJB module. One app is an end user app while the other is an admin style app. I'm having issues running both EAR files at the same time. This used to worked fine as I have tested both apps at the same time before. I don't remember the combination of server/seam/etc. when this work, so I'm trying to go back and see if I have a version of the code when it worked. It looks to be a problem with the classloader because the error I get is a class cast exception casting the object to itself. One thing that makes me think that is that the app that always work is the one that has been either loaded last (when you start the server) or hot deployed last after the server has been started. So it looks like it's grabbing the lastest class and trying to cast it to the one in the other module. Has anyone seen this before? I updated to CR1 just to make sure, but the same thing. The only strange thing that I notice in the logs besides the ClassCastException is this: | 22:59:50,488 WARN [Ejb3Configuration] Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. | I don't know where it comes from, but I'll try to find out. Any help is appreciated. Thanks, Jose View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085832#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...