axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sagara Gunathunga (JIRA)" <>
Subject [jira] [Resolved] (AXIS2-5331) Handling BigDecimals data in ADB
Date Tue, 29 May 2012 06:09:23 GMT


Sagara Gunathunga  resolved AXIS2-5331.

       Resolution: Fixed
    Fix Version/s: 1.7.0

Patch applied in r1343543. 

Though your suggestion is correct it's bit of a hard work to implement such configurable option
for one data type. But your suggestions and patches are welcome on this.  
> Handling BigDecimals data in ADB
> --------------------------------
>                 Key: AXIS2-5331
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.7.0
>         Environment: 1.7.0-SNAPSHOT
> JDK 1.6
>            Reporter: Denis Weerasiri
>              Labels: patch
>             Fix For: 1.7.0
>         Attachments: AXIS2-5330-v1.patch
> I'm facing the same issue in 1.7.0-SNAPSHOT.
> To be backward compatible axis2 adb need to use toPlainString() method provided by BigDecimal
> I have attached a patch with a test case to solve in adb.
> But what I more concerned is, whether axis2 need to handle serialization and de-serialization
of BigDecimals in a configurable manner. Suppose, a java-adb-client need to manage his input
and out data in scientific notation (in that case E-3 => 0.000), but axis2-adb always send
0.000. I feel, there should be a configurable way s.t. a client can choose to BigDecimal input/outputs
in scientific notation or plain text notation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message