This content has been marked as final. Show 2 replies
I am attempting to deploy 3 separate ear files in JBoss AS 6. These ears contain a common jar that has a Main-Class attribute in the manifest. This is causing a NameAlreadyBoundException as discussed here:
As a temporary solution, I have removed this jar and placed it into the <server config>/lib directory. However, this isn't a viable solution since we provide our ear files to somebody else. Additionally, the offending jar is not ours, so modifying the jar would potentially have licensing issues.
Is there some configuration that I can provide inside the ear files that would prevent this error from occurring?