JAX-RPC: restrictions on service exception field types?

Question

When I define a service-specific exception type that has String fields only, it works fine. But if the exception class has an int field, xrpcc complains. It also fails if I change the field to Integer.
Since JAX-RPC supports both int and Integer as operation argument and return types, I expected exceptions to be able to use these types as well. Are there restrictions on exception fields types?
Here is the class with the int fields and the xrpcc errors it generates:
public class InvalidRecordingIdException extends Exception {
     private int id;
     public InvalidRecordingIdException() {
          super();
     public InvalidRecordingIdException(int id) {
          this.id = id;
     public int getId() {
          return id;
xrpcc-server:
     [echo] Running xrpcc for the server:
     [exec] rain\RainOrder_orderRecording_Fault_SOAPSerializer.java:69:
       Method serialize(int, javax.xml.namespace.QName,
       null, com.sun.xml.rpc.streaming.XMLWriter,
       com.sun.xml.rpc.encoding.SOAPSerializationContext)
       not found in interface com.sun.xml.rpc.encoding.CombinedSerializer.
     [exec] myns2__int__int_Int_Serializer_Serializer.serialize(((
       rain.InvalidRecordingIdException)detail).getId(),
       ns1_InvalidRecordingIdException_QNAME, null, writer, context);
     [exec]                                                                ^
     [exec] rain\RainOrder_orderRecording_Fault_SOAPBuilder.java:32:
     Invalid cast from java.lang.Object to int.
     [exec] instance.setDetail(new rain.InvalidRecordingIdException((int)detail));
     [exec]                                                                         ^
     [exec] 2 errors
     ...Here's the error for the Integer field in an exception:
xrpcc-server:
     [echo] Running xrpcc for the server:
     [exec] error: generator error: generator error: java.lang.ClassCastException:
     com.sun.xml.rpc.processor.model.soap.SOAPSimpleType
     [exec] 1 error

Answer 1

You have run into a bug that will be fixed in the next release of the JWSDP dealing with Exceptions with only one member that is a primitive type. However, changing that member to a boxed (Integer) representation should work, what version of JAXRPC are you using? As a work around you should be able to eliminate the problem by adding one more member to the Exception using a different type.
Thank you for your interest in JAXRPC