Hi!

We use JBoss 7 and Wildfly 10 to publish the same web services with WSDL files generated by the server (=Bottom Up).

We noticed a slight difference between the generated WSDL files concerning the handling of optional fields/properties in the elements.

For example:

public class Example{
    private BigDecimal value;
    
    public BigDecimal getValue() { 
        return value; 
    }
}

On JBoss 7 the generated WSDL looks like this:

<xs:complexType name="Example">
    <xs:sequence>
        <xs:element name="value" nillable="true" type="xs:decimal"/>
    </xs:sequence>
</xs:complexType>

On Wildfly 10 the WSDL is generated like this:

<xs:complexType name="Example">
    <xs:sequence>
        <xs:element minOccurs="0" name="value" type="xs:decimal"/>
    </xs:sequence>
</xs:complexType>

Notice that Wildfly marks the value as optional but not nullable, whereas JBoss 7 marks it as nullable but not optional...

Is there any way to change the default behavior of the generation in JBossWS?

It would be a little cumbersome to add @XmlElement Annotations to every affected field..

Any hint would be highly appreciated,

Mathis