Hi Sam, It seems to be working OK. I can access (most) soap providers without problem. I say most because I will be submitting a question to the list soon about some problems my client calls are having, but I don't think the problems are related to using Axis the way that I am. I'm only working in SOAP client mode, not sure what would happen if I were to setup a service.
I do plan to use weblogic soap services at some point, but haven't needed to yet. --BobC -----Original Message----- From: Ayers, Sam [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 25, 2005 10:42 AM To: [email protected] Subject: RE: Weblogic 8.1.2 and Axis 1.2 Interesting... Doesn't putting the jar files ahead in the startweblogic classpath cause the weblogic server to pick up the classes in the axis jar files (instead of usting its own)? If so, does weblogic seem to behave OK running the axis classes instead of its own? Or, do you just avoid using weblogic web services if you use this technique? Sam -----Original Message----- From: Bob Carpenter [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 25, 2005 1:27 PM To: [email protected] Subject: RE: Weblogic 8.1.2 and Axis 1.2 Hi Aoife, I was NOT able to get it to work with the web.xml having this: <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> /container-descriptor> If you remove it, and place the axis jars like I mentioned below, then it should work. --BobC -----Original Message----- From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 25, 2005 8:02 AM To: '[email protected]' Subject: RE: Weblogic 8.1.2 and Axis 1.2 Hi Bob, Thanks for the reply but unfortunately no joy. I did as you suggested but that just introduced problems for my initialisation servlet. Once change since I originally posted is that I replaced the NoClassDefFoundError with a NullPointerException by also deploying the wsdl4j.jar along with the other five jars (axis.jar saaj.jar commons-logging.jar commons-discovery.jar jaxrpc.jar) in my WEB-INF\lib directory. My server now appears to get further that it did before with my client getting back an AxisFault with a faultCode of Server.userException. The start of the faultDetail is {http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException at org.apache.axis.message.MessageElement.addTextNode(Ljava.lang.String;)Ljavax .xml.soap.SOAPElement;(MessageElement.java:1387) at org.apache.axis.message.SOAPHandler.addTextNode()V(SOAPHandler.java:148) at org.apache.axis.message.SOAPHandler.endElement(Ljava.lang.String;Ljava.lang. String;Lorg.apache.axis.encoding.DeserializationContext;)V(SOAPHandler.java: 112) at org.apache.axis.encoding.DeserializationContext.endElement Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(DeserializationCont ext.java:1087) at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement ..... I did find in JIRA a bug with Axis 1.2RC2 that seems similar but from what i can read that should now be fixed so I'm really at a loss at how to proceed. I don't want to add an APP-INF directory to my deployed ear file as that is weblogic specific and I want the structure of my file to be generic so it can be deployed on either weblogic or websphere. Aoife -----Original Message----- From: Bob Carpenter [mailto:[EMAIL PROTECTED] Sent: 25 May 2005 15:01 To: [email protected] Subject: RE: Weblogic 8.1.2 and Axis 1.2 Hi Aoife, You and I are working similar problems. I posted my question on BEA's dev2dev forum. No one really had a good explanation - the axis' jars being in the WEB-INF/lib should work, but doesn't. So, someone suggested the brute-force method of adding the jars to the classpath of the app by including them in CLASSPATH of the startWebLogic.cmd. So, I added a folder <DOMAIN NAME>/lib, put the six Axis 1.2 jars there and added the six in the CLASSPATH of the app's startWebLogic.cmd and it now works. If anyone knows a more elegant way to bundle these in the EAR, please let share the info. --BobC -----Original Message----- From: Aoife Kavanagh (Ext. 987) [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 25, 2005 4:59 AM To: '[email protected]' Subject: Weblogic 8.1.2 and Axis 1.2 Hi, I'm working with Weblogic 8.1.2 and Axis 1.2 on a Windows environment. I'm deploying an EAR file that contains the following: a number of message driven beans and a war file containing an init servlet and my application libs including my axis jars. My transport is SOAP over JMS so my beans receive JMS messages which they then forward on via Axis. Using Axis 1.1 everything worked fine. Since upgrading to Axis 1.2 I'm getting a NoClassDefFoundError for org/apache/axis/description/OperationDesc in my bean. I've done some web searches and I can't find anything that fixes this. I saw the issue about the conflict between weblogic webservices.jar and Axis's saaj.jar and added the section <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> /container-descriptor> to my weblogic.xml. This makes no difference whatsoever. Is there some equivalent for the application classes? Any help appreciated. Thanks, Aoife ********************************************************************** The information contained in this e-mail is confidential, may be privileged and is intended only for the user of the recipient named above. If you are not the intended recipient or a representative of the intended recipient, you have received this e-mail in error and must not copy, use or disclose the contents of this e-mail to anybody else. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the copy you received. This e-mail has been swept for computer viruses. However, you should carry out your own virus checks. Registered in Ireland, No. 205721. http://www.FINEOS.com ********************************************************************** Learn more about Paymentech's payment processing services at www.paymentech.com THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. ..
