aspose file tools*
The moose likes Websphere and the fly likes ejb deployment issue : classnotfound error for other ejb references Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "ejb deployment issue : classnotfound error for other ejb references" Watch "ejb deployment issue : classnotfound error for other ejb references" New topic
Author

ejb deployment issue : classnotfound error for other ejb references

ravi singasani
Greenhorn

Joined: Mar 25, 2010
Posts: 6

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.

Any ideas ?
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30353
    
150

Why would you need to update it each time you make code changes? The ejb reference is changed once per ejb, not once per code change.

You really should correct the manifests to guarantee the code will deploy going forward.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
 
 
subject: ejb deployment issue : classnotfound error for other ejb references