Replying to my own message here but anyway...
I have now tried deploying this as a packaged ear file (as opposed to a using a folder called whatever.ear) but it's the same result - when it attempts to deploy the dependent jars, it complains that my core.jar is already registered.
Is it, as seems to be the case, impossible to deploy an enterprise application archive (ear) containing two or more EJB jars in JBoss? If so, this goes against the J2EE specification (see the DTD for ear files).
It may be that I am simply configuring the deployment wrongly. In that case, could someone please put me straight.
I am having some luck with the same issue, but I have not completed my deployment yet. I have been removing the references to other jar files referenced in application.xml as ejb modules from the manifest Class-Path: entries in jar files. It seems that the redundancy is the source of trouble. I will post an update if I get everything smoothed out with this attempt to let you know.
Seems to be working well for me. I hope this helps you...
Thanks Jake - that does work.
Unfortunately, it only seems to work for packaged ear files. If I try to fool it by using a folder named whatever.ear, it does not work - complaining that the dependent jar cannot find classes in the core jar. I was hoping that the latter would work because it's quicker for development to just drop in any changed jars.
I guess one of these days I am going to have to learn to use something like Ant for deployment, huh?
Anyway, thanks again,
Apologies if this message appears twice - my original posting of it has, for now at least, vanished.
Thanks Jake - you're right, removing the core jar from the classpath in the manifest does work.
Unfortunately, it only works if the ear is a packaged archive file. It does not work if I try to fool the system by using a folder called whatever.ear (which sometimes works for other stuff). I was hopeing to use the latter because it makes development easier, being able to just drop in any changed jars. I guess that I am just going to have to learn to use something like Ant for deployment, huh?
Anyway, thanks again,