The stack trace shows that com.mvcsoft.persistence.util.NamespaceUtil.getContainer is the one looking for "pm" so how is that getting bound into JNDI in 2.1 but not 2.2? What does the JNDIView MBean show about the JNDI namespace after deployment in 2.1 vs 2.2? ----- Original Message ----- From: "Jim Archer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 09, 2001 10:10 AM Subject: [JBoss-user] My stuff breaks under jBoss 2.2, not under 2.1 beta > Hi All... > > I have been working on a large app for a while and for the past several > weeks I have been working under jBoss 2.1/Tomcat beta distribution. This > morning, I down loaded jBoss2.2/Tomcat binary and fired up my app. > > The app is uses servlets in a WAR and SLSBs and BMP EBs in a jar, all bound > into an EAR. The EBs were generated using the MVC Soft EJB 2.0 persistence > manager. > > My environment is Windows 2000 and Sun's JDK 1.3. > > I deployed the exact same EAR file under both the jBoss/TC beta and the > release, and in both cases it deployed just fine. > > However, when I try to run parts of it, under the release I get naming > exceptions. I'll paste an excerpt from the server.log file below. The > exception seems to be thrown after my code successfully creates an EB and > exits its create method. My code does not use a name pm, and I looked > through the generated code and didn't find that either. > > So, this may be a problem with my code, but I wanted to post this note > since the very same EAR files runs properly under the jBoss beta Rickard > released some time ago. > > Has anyone else seen problems going from the 2.1 beta to the 2.2 release? > > Thanks! > > Jim > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
