This works for me with the changes added today. The ear structure is: test.ear/HelloNameEJB.jar/ test.ear/HelloNameEJB.jar/META-INF/ test.ear/HelloNameEJB.jar/META-INF/MANIFEST.MF test.ear/HelloNameEJB.jar/tomcattest/ejb/HelloName.class test.ear/HelloNameEJB.jar/tomcattest/ejb/HelloNameBean.class test.ear/HelloNameEJB.jar/tomcattest/ejb/HelloNameHome.class test.ear/HelloNameEJB.jar/tomcattest/EJBHomeFactory.class test.ear/HelloNameEJB.jar/tomcattest/HelloNameRemote.class test.ear/HelloNameEJB.jar/tomcattest/HelloNameTest.class test.ear/HelloNameEJB.jar/META-INF/ejb-jar.xml test.ear/HelloNameEJB.jar/META-INF/jboss.xml test.ear/HelloNameEJB.jar/META-INF/weblogic-ejb-jar.xml test.ear/web.war/META-INF/MANIFEST.MF test.ear/web.war/callEJB.jsp test.ear/web.war/index.html test.ear/web.war/WEB-INF/web.xml
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "James Higginbotham" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, April 12, 2002 10:14 AM Subject: RE: [JBoss-user] Building Catalina .sar (Tomcat to work with JBossBeta 2 HOWTO)? On the contrary, by using the testcase I emailed to the list, but modifying it to have the war inside the ear, I still get the same problem. If I remove the client jar from the war, I cannot compile the JSPs as they require the remote and home interfaces but cannot find them. So, I'm still in the same spot. Am I missing something? Did your team successfully deploy my test application in this manner? If so, can you email me the .ear file so I can see why its working for you? Any other workaround ideas? Still have an estimated date for beta 2 to be released? Thanks, James > -----Original Message----- > From: Scott M Stark [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 11, 2002 8:40 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Building Catalina .sar (Tomcat to > work with JBossBeta 2 HOWTO)? > > > This is not a Catalina integration issue. It is an issue with > the servlet 2.3 class loading model and the servlet to ejb > call being optimized when it should not be. > > By default Jetty is not using the servlet 2.3 class loading > model that loads classes from the war before the parent class > loader and so it works. If you turn on the servlet 2.3 class > loading model in Jetty it also fails. > > This behavior is not seen if the war is included in the ear > with the ejb jar and the ejb client jar left out of the war. > Is there a reason this can't be done? > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
