Yes, I have a JSP within the EAR that calls the SessionManager EJB through RMI. And that works.
I guess the real question is... has anyone else done this type of thing with my configuration? Specifically, Apache SOAP 2.2 with Weblogic 6.1 SP2 where the SOAP is trying to access a stateful session bean that resides in an EAR that is independent of the SOAP app. Right now, I'm thinking that I might just stop trying to make this work... and just WAR up the whole Apache SOAP 2.2 stuff, and include that INSIDE my EAR. --------------------John Prout wrote: > > Can you access your SessionManager EJB from something other than the SOAP > servlet ? > > (i.e is this a problem with the SOAP servlet configuration, or with the > deployment of your SessionManager EJB ?) > > -----Original Message----- > From: Michael J. Hudson [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 11, 2002 12:48 PM > To: [EMAIL PROTECTED] > Subject: Weblogic 6.1 SP2 accessing an EJB in an EAR > > I originally had Apache SOAP 2.2 working just fine with Weblogic > 5.1... and there, it was successfully accessing a stateful session > bean. Now, after a series of problems trying to upgrade to Weblogic > 6.1, I have one last problem and I think things will work again. > BTW, I'm using Weblogic 6.1 SP2. > > My current problem is that the SOAP stuff can't seem to find my stateful > session bean anymore. > > I get the following error: > > <ECHO> Fri Jan 11 14:53:16 EST 2002:<E> Generated fault: > <ECHO> Fri Jan 11 14:53:16 EST 2002:<E> Fault Code = SOAP-ENV:Server > <ECHO> Fri Jan 11 14:53:16 EST 2002:<E> Fault String = Error in > connecting to EJB > java.lang.ClassNotFoundException: > org.myapp.services.ejb.sessionmanager.SessionManagerHome > > I have my application wrapped in an EAR file. And thus, all my > EJBs are in that EAR file... and thus my SessionManager bean is and > does NOT need to be my classpath. > > At first, I figured the problem was that I needed to modify the web.xml > so that the <ejb-ref-name> points to my sessionmanager... and likewise > also create weblogic.xml that tied the web.xml's <ejb-ref-name> to > the actual JNDI name. I thought that would do it... but no such luck. > > Am I missing something. Is there some other trick in telling an > outside web app like Apache SOAP where my EAR is... or how to obtain > an EJB in my EAR? > > Thanks > > ------------------------------------- > Michael J. Hudson > Software/Framework Engineer > [EMAIL PROTECTED] > > cell-phone: 703.362.8039 > voice-mail: 703.827.0638 ext. 4786 > fax: 703.734.0987 > > Blueprint Technologies > "Great software starts with great architecture" > http://www.blueprinttech.com
