Well the issue has been resolved. Apparently, it was not due to Tomcat being embedded at all. It was due to multiple versions of myfaces and sun jars within the WEB-INF/lib directory of the war file.
Thanks to Volker Weber on the myFaces list for finding the problem. He removed duplicate jars from the war file and when I dropped in his revised war, the test managed bean worked right away. John -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Friday, February 03, 2006 3:21 PM To: Tomcat Users List Subject: RE: Managed beans not instantiated with embedded Tomcat 5.5.15 > From: John [mailto:[EMAIL PROTECTED] > Subject: Managed beans not instantiated with embedded Tomcat 5.5.15 > > The web application makes use of managed beans > > This web application works fine when run in a Stand Alone Tomcat that > is not embedded. > > When the web application is run within our embedded Tomcat, the > managed beans are not instantiated although no errors are produced. The standalone Tomcat configuration includes these two listeners: <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /> <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /> Are they enabled when you run Tomcat embedded? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
