How to get rid of throwing an instance in SOAP UI?

Question

Java

While working with SOAP, I encountered the following problem. Spring-ws independently generates wsdl for me according to the available classes. everything was fine and peaceful, until the moment when the scheme needed to be expanded and implemented tokens and authorization. now Soap UI throws an Execution when trying to update the schema. through trial and error, the source of the troubles was found.
Soap ui crits after I add a String token to one of the requests, the request takes the following form.

@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "", propOrder = {})
@XmlRootElement(namespace = "http://www.kickidler.com/soap")
public class OrderFinishedRequest {
  
  private String token;
  
  private List<FinishedOrderEvent> orderList;

  public List<FinishedOrderEvent> getOrderList() {
    return orderList;
  }

  public void setOrderList(List<FinishedOrderEvent> orderList) {
    this.orderList = orderList;
  }

  public String getToken() {
    return token;
  }

  public void setToken(String token) {
    this.token = token;
  }

}

wsdl looks like this

<xs:element name="orderFinishedRequest">
<xs:complexType>
<xs:all>
<xs:element form="qualified" minOccurs="0" name="token" type="xs:string"/>
<xs:element form="qualified" maxOccurs="unbounded" minOccurs="0" name="orderList" type="tns:finishedOrderEvent"/>
</xs:all>
</xs:complexType>
</xs:element>

in this state, Soap ui starts to crit and does not load the scheme. if only one of the two elements is present in the request, everything is fine and good. no problem. what could be the problem?

Answer 1

found a way out - Soap UI does not like <xs:all>it, and spring, in the absence of an explicitly specified propOrder, generates exactly <xs:all>. by explicitly specifying the order <xs:all>was replaced by sequence, after which the scheme was successfully eaten by SOAP ui

Answer 2

Can you post a stacktrace?
Does the old wsdl also look like this (only without the token)?