如何拥有两个具有不同命名空间和相同 JAXB 类的不同端点？
Posted
技术标签:
【中文标题】如何拥有两个具有不同命名空间和相同 JAXB 类的不同端点？【英文标题】：How can I have two different endpoint with different namespace and same JAXB class? 【发布时间】：2018-01-16 21:56:34 【问题描述】：我正在使用弹簧皂 ws。
我有以下 JAXB 域类对应于复杂类型
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder =
"reference",
"reason"
)
@XmlRootElement(name = "request-message")
public class RequestMessageType
@XmlElement(name = "reference", required = true)
protected String reference;
@XmlElement(name = "reason")
protected String reason;
// I have getters and setters but removed here.
我有以下带有@XmlRegistry 注释的类
@XmlRegistry
public class ObjectFactory
private final static QName _RequestMessage_QNAME = new QName("http://namespace/url", "request-message");
public ObjectFactory()
@XmlElementDecl(namespace = "http://namespace/url", name = "request-message")
public JAXBElement<RequestMessageType> createDisconnectRequestMessage(RequestMessageType value)
return new JAXBElement<RequestMessageType>(_RequestMessage_QNAME, RequestMessageType.class, null, value);
以下是端点
@Endpoint
public class FirstEndPoint
private static final String NAMESPACE_URI = "http://first/url/version";
private static final Logger LOG = Logger.getLogger(FirstEndPoint.class);
@PayloadRoot(namespace = NAMESPACE_URI, localPart = "request-message")
@ResponsePayload
public JAXBElement<ResponseMessageType> requestMessage(@RequestPayload JAXBElement<RequestMessageType> requestMessage)
LOG.info("request-message : first version ID : " + requestMessage.getValue().getReference());
//Preparing response and return response
@Endpoint
public class SecondEndPoint
private static final String NAMESPACE_URI = "http://second/url/version";
private static final Logger LOG = Logger.getLogger(SecondEndPoint.class);
@PayloadRoot(namespace = NAMESPACE_URI, localPart = "request-message")
@ResponsePayload
public JAXBElement<ResponseMessageType> requestMessage(@RequestPayload JAXBElement<RequestMessageType> requestMessage)
LOG.info("request-message : second version ID : " + requestMessage.getValue().getReference());
//Preparing response and return response
当我发出 Soap 请求时，我使用的是在 soap 请求的端点中给出的 NAMESPACE_URI。
在这里，在这种情况下，我得到以下响应
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring xml:lang="en">unexpected element (uri:"http://first/url/version", local:"request-message"). Expected elements are <http://namespace/urlrequest-message></faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
如果我在端点和soap请求中使用“http://namespace/url”作为NAMESPACE_URI，我会得到正确的响应，但我尝试让具有两个不同命名空间的两个端点不同，然后它不起作用并给出上述响应。
如何为具有相同 JAXB 类的两个不同端点使用两个不同的命名空间？我对 Spring 和 Web 服务完全陌生。
附加信息：RequestMessageType 类和 ObjectFactory 类在一个包中，并且在 package-info.java 命名空间中
@javax.xml.bind.annotation.XmlSchema(namespace="http://namespace/url",elementFormDefault=javax.xml.bind.annotation.XmlNsForm.QUALIFIED)
package com.example
我需要更改 package-info.java 文件中的任何内容吗？
【问题讨论】：
我很高兴也能看到您生成的 WSDL 在任何情况下，在我的模式中，我都会定义两个请求和响应元素。这些元素将属于同一类型。如果你愿意，我有时间可以在我的 github 帐户上分享一个简单的项目 我建议创建一个 RequestMessageType 抽象，并创建 2 个类来扩展它。这些课程单独注册。通过这样做：您的 wsdls 将具有不同的命名空间，但您的服务层可以保持不变。 【参考方案1】：我创建了一个示例项目。我希望它对你有用。你可以在这里看看：https://github.com/angeloimm/spring-ws-sample 基本上这是我的 WSDL 文件（在 SOAP Web 服务中，所有内容都由 WSDL 控制）：
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:ss="http://www.example.org/SpringSample/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="SpringSample"
targetNamespace="http://www.example.org/SpringSample/">
<wsdl:types>
<xsd:schema targetNamespace="http://www.example.org/SpringSample/">
<xsd:complexType name="abstractRequest">
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element name="reqName" type="xsd:string" nillable="false"
maxOccurs="1" minOccurs="1" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="abstractResponse">
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element name="responseName" type="xsd:string"
nillable="false" maxOccurs="1" minOccurs="1" />
</xsd:sequence>
</xsd:complexType>
<xsd:element name="requestImplementation" type="ss:abstractRequest" />
<xsd:element name="responseImplementation" type="ss:abstractResponse" />
<xsd:element name="requestImplementation2" type="ss:abstractRequest" />
<xsd:element name="responseImplementation2" type="ss:abstractResponse" />
</xsd:schema>
</wsdl:types>
<wsdl:message name="OperationRequest">
<wsdl:part element="ss:requestImplementation" name="request" />
</wsdl:message>
<wsdl:message name="OperationResponse">
<wsdl:part element="ss:responseImplementation" name="response" />
</wsdl:message>
<wsdl:message name="OperationRequest2">
<wsdl:part element="ss:requestImplementation2" name="request2" />
</wsdl:message>
<wsdl:message name="OperationResponse2">
<wsdl:part element="ss:responseImplementation2" name="response2" />
</wsdl:message>
<wsdl:portType name="SpringSample">
<wsdl:operation name="Operation1">
<wsdl:input message="ss:OperationRequest" />
<wsdl:output message="ss:OperationResponse" />
</wsdl:operation>
<wsdl:operation name="Operation2">
<wsdl:input message="ss:OperationRequest2" />
<wsdl:output message="ss:OperationResponse2" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SpringSampleSOAP" type="ss:SpringSample">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="Operation1">
<soap:operation style="document" soapAction="http://www.example.org/SpringSample/Operation1" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="Operation2">
<soap:operation style="document" soapAction="http://www.example.org/SpringSample/Operation2" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SpringSample">
<wsdl:port binding="ss:SpringSampleSOAP" name="SpringSampleSOAP">
<soap:address location="http://www.example.org/" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
如您所见，我定义了 2 个复杂类型：abstractRequest 和 abstractResponse。然后我通过使用元素requestImplementation,requestImplementation2,responseImplementation,responseImplementation2实现它们根据 WS-I 规范，您需要使用单独的操作和元素
然后我写了这个端点：
@Endpoint
public class SampleEndpoint
private static final Logger logger = LoggerFactory.getLogger(SampleEndpoint.class.getName());
private static final String NAME_SPACE_URI = "http://www.example.org/SpringSample/";
@PayloadRoot(namespace = NAME_SPACE_URI, localPart="requestImplementation")
@ResponsePayload
public JAXBElement<AbstractResponse> operationOneResp(@RequestPayload JAXBElement<AbstractRequest> ar)
if( logger.isDebugEnabled() )
logger.debug("Operation 1 request "+ar.getValue().getReqName());
ObjectFactory of = new ObjectFactory();
AbstractResponse aResp = of.createAbstractResponse();
aResp.setResponseName("operation 1 response");
JAXBElement<AbstractResponse> result = of.createResponseImplementation(aResp);
return result;
@PayloadRoot(namespace = NAME_SPACE_URI, localPart="requestImplementation2")
@ResponsePayload
public JAXBElement<AbstractResponse> operationTwoResp(@RequestPayload JAXBElement<AbstractRequest> ar)
if( logger.isDebugEnabled() )
logger.debug("Operation 2 request "+ar.getValue().getReqName());
ObjectFactory of = new ObjectFactory();
AbstractResponse aResp = of.createAbstractResponse();
aResp.setResponseName("operation 2 response");
JAXBElement<AbstractResponse> result = of.createResponseImplementation(aResp);
return result;
正如你现在所看到的，我总是在这两种方法中使用AbstractRequest 和AbstractResponse JAXBElement。这两种方法也可以在 2 个不同的端点中
我希望它是你需要的并且有用
安杰洛
【讨论】：
以上是关于如何拥有两个具有不同命名空间和相同 JAXB 类的不同端点？的主要内容，如果未能解决你的问题，请参考以下文章