Java实现多SOAP服务动态调用的方案咨询（含模拟器开发需求）

Hey there! Let's figure out how to dynamically call those 4 SOAP operations from your WSDL instead of hardcoding XML. I’ve got a couple of tried-and-true approaches that should work perfectly for your Java simulator:

This is my go-to for dynamic SOAP calls because it’s built into Java (no extra libraries needed) and lets you call any operation from your WSDL without pre-generating client classes. Here’s how to implement it in your servlet:

• Step 1: Initialize the Service from your WSDL
  First, load the WSDL at runtime and create a Service instance. You’ll need the WSDL path/URL and the service’s QName (you can find this in your WSDL under the <wsdl:service> tag).

  // In your servlet's init() method (reuse this instance!)
  URL wsdlUrl = new URL("file:///path/to/your/wsdl-file.wsdl");
  QName serviceQName = new QName("http://your-target-namespace.com", "YourServiceName");
  Service soapService = Service.create(wsdlUrl, serviceQName);
  

• Step 2: Create a Dispatch handler
  Use Dispatch<SOAPMessage> to handle raw SOAP messages dynamically. You’ll also need the port QName (from <wsdl:port> in your WSDL).

  QName portQName = new QName("http://your-target-namespace.com", "YourPortName");
  Dispatch<SOAPMessage> dispatch = soapService.createDispatch(portQName, SOAPMessage.class, Service.Mode.MESSAGE);
  

• Step 3: Build & send dynamic requests
  Instead of hardcoding XML, construct the SOAP body on-the-fly based on which operation you want to call. For example, to invoke an operation named GetUserDetails:

  // Create a blank SOAP message
  SOAPMessageFactory msgFactory = SOAPMessageFactory.newInstance();
  SOAPMessage soapRequest = msgFactory.createMessage();
  SOAPBody soapBody = soapRequest.getSOAPPart().getEnvelope().getBody();
  
  // Add the operation element dynamically
  QName operationQName = new QName("http://your-target-namespace.com", "GetUserDetails");
  SOAPElement operationElement = soapBody.addChildElement(operationQName);
  
  // Add parameters matching the operation's schema
  SOAPElement userIdElement = operationElement.addChildElement("UserId");
  userIdElement.addTextNode(request.getParameter("user-id")); // Pull from servlet request
  
  // Set the SOAP action (found in WSDL's operation binding)
  soapRequest.getMimeHeaders().addHeader("SOAPAction", "http://your-target-namespace.com/GetUserDetails");
  soapRequest.saveChanges();
  
  // Send the request and get the response
  SOAPMessage soapResponse = dispatch.invoke(soapRequest);
  // Parse the response to send back from your servlet
  

If you’re open to using external libraries, Apache Axis2 offers a robust dynamic client that simplifies handling multiple SOAP operations:

• Add Axis2 dependencies
  If using Maven, include these in your pom.xml:

  <dependency>
      <groupId>org.apache.axis2</groupId>
      <artifactId>axis2-kernel</artifactId>
      <version>1.8.2</version>
  </dependency>
  <dependency>
      <groupId>org.apache.axis2</groupId>
      <artifactId>axis2-adb</artifactId>
      <version>1.8.2</version>
  </dependency>
  

• Dynamic invocation code

  // Initialize once in servlet init()
  ConfigurationContext configContext = ConfigurationContextFactory.createDefaultConfigurationContext();
  ServiceClient serviceClient = new ServiceClient(configContext, null);
  EndpointReference targetEPR = new EndpointReference("http://your-soap-service-endpoint-url");
  serviceClient.getOptions().setTo(targetEPR);
  
  // For each request in your servlet:
  serviceClient.getOptions().setAction("http://your-target-namespace.com/YourOperationName");
  
  // Build the request payload dynamically
  OMFactory omFactory = OMAbstractFactory.getOMFactory();
  OMNamespace omNs = omFactory.createOMNamespace("http://your-target-namespace.com", "ns");
  OMElement operationElement = omFactory.createOMElement("YourOperationName", omNs);
  
  // Add parameters
  OMElement paramElement = omFactory.createOMElement("ParamName", omNs);
  paramElement.setText(request.getParameter("param-value"));
  operationElement.addChild(paramElement);
  
  // Send request and get response
  OMElement responseElement = serviceClient.sendReceive(operationElement);
  // Process response as needed
  

• Reuse instances: Don’t create a new Service or ServiceClient for every servlet request—initialize them once in the init() method to boost performance.
• Validate inputs: Since you’re building requests dynamically, add checks to ensure parameters match the WSDL’s schema (e.g., required fields, data types).
• Handle errors: Wrap SOAP calls in try-catch blocks to handle SOAPException, IOException, or service-specific faults gracefully.

Pro Tip: For even more flexibility, you can parse the WSDL programmatically using Apache XML Schema (xmlschema-core) to auto-discover operation names and parameters. This way you won’t have to hardcode QNames or parameter names at all!

内容的提问来源于stack exchange，提问作者tanvi