[
https://issues.apache.org/jira/browse/AXIS2-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Weerasiri updated AXIS2-5331:
-----------------------------------
Environment:
1.7.0-SNAPSHOT
JDK 1.6
was:1.7.0-SNAPSHOT
> Handling BigDecimals data in ADB
> --------------------------------
>
> Key: AXIS2-5331
> URL: https://issues.apache.org/jira/browse/AXIS2-5331
> 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
> Attachments: AXIS2-5330-v1.patch
>
>
> I'm facing the same issue https://issues.apache.org/jira/browse/AXIS2-4036 in
> 1.7.0-SNAPSHOT.
> To be backward compatible axis2 adb need to use toPlainString() method
> provided by BigDecimal API.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
