我从一些遗留代码接收SOAP请求，并使用来自遗留代码使用的相同WSDL的JAX-WS生成的对象来处理它，但是当我处理请求时，我得到一个Unmarshalling Error：意外的元素错误。
此请求的WSDL部分如下:(请注意“schema”已替换我们的WSDL的所有实际模式位置）
<xsd:complexType name="Administrate">
<xsd:sequence>
<xsd:element name="AdminOperation" type="typens:AdminOperation" maxOccurs="unbounded" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Administrate" type="typens:Administrate"/>
<xsd:complexType name="AdministrateResponse">
<xsd:sequence>
<xsd:element name="Status" type="typens:SoapResponseStatus"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="AdministrateResponse" type="typens:AdministrateResponse"/>
<xsd:complexType name="AdminOperation">
<xsd:sequence>
<xsd:choice>
<xsd:element name="Transaction" type="typens:Transaction" minOccurs="0"/>
<xsd:element name="CreateUser" type="typens:CreateUser" minOccurs="0"/>
<xsd:element name="DeleteUser" type="typens:DeleteUser" minOccurs="0"/>
<xsd:element name="UpdateUser" type="typens:UpdateUser" minOccurs="0"/>
<xsd:element name="CreateGroup" type="typens:CreateGroup" minOccurs="0"/>
<xsd:element name="DeleteGroup" type="typens:DeleteGroup" minOccurs="0"/>
<xsd:element name="UpdateGroup" type="typens:UpdateGroup" minOccurs="0"/>
<xsd:element name="CreateChannel" type="typens:CreateChannel" minOccurs="0"/>
<xsd:element name="DeleteChannel" type="typens:DeleteChannel" minOccurs="0"/>
<xsd:element name="UpdateChannel" type="typens:UpdateChannel" minOccurs="0"/>
<xsd:element name="CreateRole" type="typens:CreateRole" minOccurs="0"/>
<xsd:element name="DeleteRole" type="typens:DeleteRole" minOccurs="0"/>
<xsd:element name="UpdateRole" type="typens:UpdateRole" minOccurs="0"/>
<xsd:element name="CreateFileType" type="typens:CreateFileType" minOccurs="0"/>
<xsd:element name="DeleteFileType" type="typens:DeleteFileType" minOccurs="0"/>
<xsd:element name="UpdateFileType" type="typens:UpdateFileType" minOccurs="0"/>
<xsd:element name="CreateFolder" type="typens:CreateFolder" minOccurs="0"/>
<xsd:element name="DeleteFile" type="typens:DeleteFile" minOccurs="0"/>
<xsd:element name="MoveFile" type="typens:MoveFile" minOccurs="0"/>
<xsd:element name="CopyFile" type="typens:CopyFile" minOccurs="0"/>
<xsd:element name="UpdateFile" type="typens:UpdateFile" minOccurs="0"/>
<xsd:element name="DeleteJob" type="typens:DeleteJob" minOccurs="0"/>
<xsd:element name="DeleteJobNotices" type="typens:DeleteJobNotices" minOccurs="0"/>
<xsd:element name="UpdateJobSchedule" type="typens:UpdateJobSchedule" minOccurs="0"/>
<xsd:element name="UpdateVolumeProperties" type="typens:UpdateVolumeProperties" minOccurs="0"/>
<xsd:element name="UpdateOpenSecurityCache" type="typens:UpdateOpenSecurityCache" minOccurs="0"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
并发送请求：
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns="schema">
<SOAP-ENV:Header>
<AuthId>7</AuthId>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<Administrate>
<UpdateFile>
<SetPermissions>
<Permission SOAP-ENC:arrayType="Permission[1]">
<UserName>username</UserName>
<AccessRight>rights</AccessRight>
</Permission>
</SetPermissions>
<NameList>
<String>folder1</String>
<String>folder1/folder2</String>
<String>folder1/folder2/file.ext</String>
</NameList>
</UpdateFile>
</Administrate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
但是我的代码中出现以下错误：
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Unmarshalling Error: unexpected element
(uri:"schema", local:"UpdateFile"). Expected elements
are <{schema}AdminOperation> </faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Administrate JAX-WS生成的对象只包含带有getter的AdminOperations的ArrayList，
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "Administrate", propOrder = {
"adminOperation"
})
public class Administrate {
@XmlElement(name = "AdminOperation")
protected List<AdminOperation> adminOperation;
/**
* Gets the value of the adminOperation property.
*
* <p>
* This accessor method returns a reference to the live list,
* not a snapshot. Therefore any modification you make to the
* returned list will be present inside the JAXB object.
* This is why there is not a <CODE>set</CODE> method for the adminOperation property.
*
* <p>
* For example, to add a new item, do as follows:
* <pre>
* getAdminOperation().add(newItem);
* </pre>
*
*
* <p>
* Objects of the following type(s) are allowed in the list
* {@link AdminOperation }
*
*
*/
public List<AdminOperation> getAdminOperation() {
if (adminOperation == null) {
adminOperation = new ArrayList<AdminOperation>();
}
return this.adminOperation;
}
}
但是从发送的遗留请求和从WSDL发出的遗留请求来判断，该操作标记被替换为操作选择，例如，更新文件等吗？
由于我无法更改遗留请求或遗留WSDL，因此我不确定如何继续。任何帮助将不胜感激，所以提前感谢！
答案 0 :(得分：1)
你的怀疑是正确的。在这种情况下，客户端实际上发送的请求不符合提供的架构。
由于您无法控制客户端代码并且显然必须容纳客户端，因此我希望它是此服务的唯一客户端。最简单的路径是将服务调整为客户实际构建的合同。您可以手动调整模式以指示UpdateFile是Administrate的子项，然后重新生成相关对象或（不打扰对象的重新生成）调整Administrate java对象注释以将FileUpdate反映为第一级子项： ... @XmlType（name =“Administrate”，propOrder = { “updateFile” }） 公共类管理{
@XmlElement(name = "UpdateFile")
protected UpdateFileType updateFile;
...
尽职调查还要认识到其他形式的请求（它们是否符合合同），以确保在调整服务端点时不会再发生破坏。