0 Replies Latest reply on May 3, 2007 11:49 AM by Randal Cobb

    Packed EAR problems deploying in 4.2.0.CR2

    Randal Cobb Newbie

      Hello all,

      I have an app that I am porting from 4.0.4 to 4.2.0.CR2... Our ear file contains several jar files and three war files. The ear seems to deploy properly in 4.2.0 (i.e., no exceptions during deploy), but does not seem to run properly. The login page displays, but, when the users click on "login" after entering their credentials, they get an exception: javax.naming.NameNotFoundException when looking for the login service bean (EJB3 session bean).

      I experimented a little and the app does seem to deploy properly and run properly if we expand the ear file and deploy the exploded application. We don't get any of the naming exceptions we see when we deploy the unexploded ear file.

      Could I be doing something wrong? Are there any known problems with the deployment code for ear files?

      Thanks in advance!