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
