Re: Which Axis for WebLogic 9.1?
Maybe you have a similar problem compared to http://ws.apache.org/axis/java/install.html#WebLogic8.1 WebLogic 8.1 ships with webservices.jar that conflicts with Axis' saaj.jar and prevents Axis 1.2 from working right out of the box. This conflict exists because WebLogic uses an older definition of javax.xml.soap.* package from Java Web Services Developer Pack Version 1.0 http://java.sun.com/webservices/docs/1.0/api/javax/xml/soap, whereas Axis uses a newer revision from J2EE 1.4. Hendrik Schreiber wrote: Hey, We are currently upgrading from WebLogic 8.1 to 9.1 and one of the things that stopped working is Axis 1.1. We are seeing the following NullPointerException in the Call class: java.lang.NullPointerException at org.apache.axis.client.Call.invoke(Call.java:1768) at com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReportClient.java:738) at com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient.java:255) ... Apparently this is linked to WebLogic prefering its own saaj classes. In fact when we prepend the saaj jar that comes with Axis 1.1 to the WebLogic classpath, things work out. However, that is unfortunately not an option for us. So what I was wondering is the following: - Has anyone figured out what's the best way to get Axis (preferably 1.1) to run with WebLogic 9.1? - Is there a version of Axis that works smoothly with WebLogic 9.1? - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3? Thanks for your help! -hendrik
Axis 1.3 document literal and no parts in the message
I got stuck in a discussion between two consultants if Axis 1.3 fulfills the WSDL 1.1 specification for document/literal correctly. Consultant 1: Taken from http://www.w3.org/TR/wsdl#_messages (2.3 Messages) the message is defined by Messages consist of one or more logical parts.. Consultant 2: On the other hand the WSDL schema definition in http://www.w3.org/TR/wsdl#A4.1 defines wsdl:part with element ref=wsdl:part minOccurs=0 maxOccurs=unbounded/ Consultant 1: This maybe contradictory, but this is because WSDL may use either by rpc or document styles. Per RPC, of course, message may be without any part. Unfortunately, this is not the case with document style. For document style only the message part are sent. No other leading information is used. Thus, the inner message-parts in this case are must. One MUST NOT discard message-parts when document style is used. Me: We have a message getAllSectors defined as wsdl:message name=getAllSectorsRequest /wsdl:message Thus, no part is defined. Axis 1.3 create the following http request: ?xml version=1.0 encoding=UTF-8?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;soapenv:BodygetAllSectors xmlns=urn:remote.ws.mycompany.org//soapenv:Body/soapenv:Envelope What do you think? Is there a problem in our wsdl file or is this a bug in Axis 1.3 by using document/literal?
