Java 运行axis2客户端1.5版

因此，我已经没有办法让客户机连接到通过axis2运行的SOAP服务

我尝试了两种方法，一种是使用wsdl2java构建存根和相关的客户端类，然后编写一个客户端类来构建请求消息并通过存根发送它们。另一种方法是使用ServiceClient进行连接

两人都在以各自的方式失败

选项#1，每次通过存根发送消息时，我都会得到以下信息：

org.apache.axis2.AxisFault: The input stream for an incoming message is null.
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87)
at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)

选项#2，每次运行时都会出现以下异常：

org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.local.LocalTransportSender

选项2来源：

import javax.xml.stream.XMLStreamException;
import org.apache.axiom.om.OMAbstractFactory; 
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.Constants;
import org.apache.axis2.client.ServiceClient;

public class loyaltyClient {

    private static EndpointReference targetEPR = 
         new EndpointReference(
           "http://localhost:8080/axis2/services/service");

    public static OMElement verifyCustomer(String customer_id) {
        OMFactory fac = OMAbstractFactory.getOMFactory();
        OMNamespace omNs = fac.createOMNamespace(
                "http://localhost/", "service");
        OMElement method = fac.createOMElement("VerifyCustomer", omNs);
        OMElement value1 = fac.createOMElement("customer_id",omNs);
        OMElement value2 = fac.createOMElement("source_id",omNs);
        OMElement value3 = fac.createOMElement("source_password",omNs);
        OMElement value4 = fac.createOMElement("source_txnid",omNs);
        OMElement value5 = fac.createOMElement("timestamp",omNs);

value1.addChild(fac.createOMText(value1, customer_id));
value2.addChild(fac.createOMText(value2, "source"));
value3.addChild(fac.createOMText(value3, "1234"));
value4.addChild(fac.createOMText(value4, "123"));
value5.addChild(fac.createOMText(value5, "06-01-2010 12:01:01"));
        method.addChild(value1);
        method.addChild(value2);
        method.addChild(value3);
        method.addChild(value4);
        method.addChild(value5);
        return method;
    }

    public static void main(String[] args) {
        try {
            OMElement vctest = loyaltyClient.verifyCustomer("6177740603");
            Options options = new Options();
            options.setTo(targetEPR);

options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

            ServiceClient sender = new ServiceClient();
            sender.setOptions(options);
            OMElement result = sender.sendReceive(vctest);

            String response = result.getFirstElement().getText();
            System.out.println(response);

        } catch (Exception e) { //(XMLStreamException e) {
            System.out.println(e.toString());
        }
    }

---

}

有一点需要注意，Axis2是一个，我最近不得不编写Axis2客户端，发现使用默认构造函数效果不好——我必须手动创建配置上下文，等等。我发现使用

ServiceClient.getOptions（）

而不是创建

新选项（）

保留了一些默认数据。我还建议删除

选项。setTransportInProtocol（…）

，除非您真的需要它——没有这个选项，一切都可以通过HTTP正常工作。此外，您可能需要设置

options.setAction（…）

以与WSDL中的“操作”相对应

我已经包括了我的大部分客户（去掉了敏感信息），希望能有所帮助。除非您计划使用WS-addressing，否则您可能可以安全地忽略有关寻址的部分

ConfigurationContext cfgCtx = null;

try {
    /* Passing null to both params causes an AxisConfiguration to be created that uses
     * the default axis2.xml file, which is included in the axis2 distribution jar.
     * This is ideal for our case, since we cannot pass a full file path (relative
     * paths are not allowed) because we do not know where the customer will deploy
     * the application. This also allows engaging modules from the classpath. */
    cfgCtx = ConfigurationContextFactory.createConfigurationContextFromFileSystem(null , null);
} catch (AxisFault e) {
    // Bubble up the error
}

ServiceClient svcClient = null;
try {
    svcClient = new ServiceClient(cfgCtx, null);
} catch (AxisFault e) {
    // Bubble up the error
}

try {
    /* This will work with the above ConfigurationContext as long as the module
     * (addressing-1.5.1.mar) is on the classpath, e.g. in shared/lib. */
    svcClient.engageModule("addressing");
} catch (AxisFault e) {
    // Bubble up the error
}

Options opts = svcClient.getOptions();
opts.setTo(new EndpointReference("http://myservername:8080/axis2/services/MyService"));
opts.setAction("urn:doSomething"); // Corresponds to the "operation" in MyService's WSDL
opts.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI); // Set output to SOAP 1.2

SOAPFactory factory = OMAbstractFactory.getSOAP12Factory();
svcClient.addHeader(createSOAPSecurityHeader(factory, response)); // CreateSOAPHeader just creates an OMElement

try {
    svcClient.sendReceive(createSOAPBody(factory, response)); // CreateSOAPBody just creates an OMElement
} catch (AxisFault e) {
    throw new ResponseDeliveryException(1, "Error sending SOAP payload.", e);
}

---

在使用Axis连接到.Net服务提供商时，我还遇到了错误“传入消息的输入流为null”

问题是.Net不支持名为“分块编码”的功能，默认情况下，Axis会将其请求头分块，这被认为是HTTP 1.1兼容的东西

无论如何，您可以通过执行以下操作在Axis中关闭此功能：

// Turn off the Axsis Chunked feature, some service providers (like .Net) don't support chunked headers.
Options options = serviceClient.getOptions();
options.setProperty(HTTPConstants.CHUNKED, Constants.VALUE_FALSE);
serviceClient.setOptions(options);            

这对我有用。处理.Net服务时要确保的另一件事是能够指定端口名，并确保消息负载具有每个元素的名称空间前缀

希望这些信息能帮助别人

干杯，

---

DC

你发现选项1有问题吗？我也有同样的问题。也支持这一说法。显然，人们已经在这方面取得了成功，但我个人在上面的问题中转向了ApacheCXF，没有理由回头看。