Previous releases of JBoss EAP 6 carried an issue that presented when an `Exception` class contained some members with type parameters defined as shown the following example.
The WSDL generated from the exception class was incorrect and the SOAP fault message was not expected.
----
@javax.xml.ws.WebFault
public class GenericsException extends Exception {
private static final long serialVersionUID = 1L;
private ObjectWithGenerics<Boolean, Integer> obj;
public ObjectWithGenerics<Boolean, Integer> getObj() {
return obj;
}
public void setObj(ObjectWithGenerics<Boolean, Integer> obj) {
this.obj = obj;
}
}
----
This issue was resolved upstream and the fix incorporated into this release of the product.
When the Exception has some generics object like:
@javax.xml.ws.WebFault
public class GenericsException extends Exception {
private static final long serialVersionUID = 1L;
private ObjectWithGenerics<Boolean, Integer> obj;
public ObjectWithGenerics<Boolean, Integer> getObj() {
return obj;
}
public void setObj(ObjectWithGenerics<Boolean, Integer> obj) {
this.obj = obj;
}
}
Both the wsdl generated from the exception class is wrong and soap fault message is not expected.
When the Exception has some generics object like: @javax.xml.ws.WebFault public class GenericsException extends Exception { private static final long serialVersionUID = 1L; private ObjectWithGenerics<Boolean, Integer> obj; public ObjectWithGenerics<Boolean, Integer> getObj() { return obj; } public void setObj(ObjectWithGenerics<Boolean, Integer> obj) { this.obj = obj; } } Both the wsdl generated from the exception class is wrong and soap fault message is not expected.