I have two EJB jars packaged into a EAR. say EJb1.jar and Ejb2.jar. I am deploying it in WebSphere 7.0. Ejb1 is referencing to classes in Ejb2.jar. Unless I specify the Ejb2.jar in Manifest.MF file of Ejb1.jar, the deployment of EAR file fails.
Throws error that build path is incomplete and that referenced class is not found.I see the current EAR setup working fine with my other team members and other development environments.
Is there any configurable change I can do ? at WebSphere console ? To make it ignore the reference issues ?
I have too many ejb's in this ear referencing each other. It makes things really difficult to update manifest file each time we make code changes.