I have a situation where a session bean (call it Bean A) is defined in an external jar that I have no control over. This bean is used by other beans in that jar.
I wish to override the behaviour of this bean A and therefore, I have created another session bean and have named it A. This is because the other beans in the external jar relie on the bean with name A.
So I have a EAR file with the external jar and my A.class file. Deploying on JBoss throws the Bean already registered error. Is there any way to get JBoss to not deploy the bean from the external jar?
Or do you have another solution for the situation I have?