I have multiple Session beans with the same class names being deployed to JBoss on a Linux box. The jar files, JNDI Names, EJB Names (ejb-jar.xml,jboss.xml) are all named differently. The files are deployed to subdirectories with server/default/deploy.
When I call methods on these Beans, I receive a 'method not found error'. Where the methods in the Beans have the ~same~ signature, it appears that the first bean to be deployed is being called, despite the fact that the remote Home lookup is on a ~different~ bean.
It appears to be a straight out class conflict. and hence bug in JBoss. Any ideas how to overcome this?
Do the same name classes also have equal bytecode implementation or are they in fact different implementations under the same name?