Skip to main content

Corrupted data after

1 reply [Last post]
Joined: 2003-06-16

My project just encountered the following errors when receiving a 40KB+ SOAP message.

1. NumberFormatException on a attribute value defined as xs:int.

2. A xs:string attribute value is different when logged as a handler before the unmarshalling process, and when printed later in the application codes.

We're using the EA1 of JAX-RPC 2.0. Does anyone know if this is a known bug/issue with EA1? And if it is already fixed in EA2?

Really appreciate any information regarding the above.

Thanks in advance.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2003-06-16

Mathew, EA 1 is extremely old code. Please try the latest nightly build at: