| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| xs:double - Exponential |
« View previous topic :: View next topic » |
| Author |
Message
|
| SKK |
 Posted: Mon Sep 10, 2007 3:25 am Post subject: xs:double - Exponential |
 |
|
Acolyte
Joined: 09 May 2005
Posts: 67
|
Hi,
We have a message set, which is created from XSD. In this there is a field with type as "xs:double". At both source and target, we use the same message set, when we give input as "1.414", on the output side it becomes "1.414E0". This is just a routing, there is no transformation. When checked in messageset, there is no option of specifying the precision or exponential for xs:double., is there way, we can specify precision limit for xs:double in message set
_________________
Regards,
SKK |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Sep 10, 2007 5:56 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
1.414E0 is exactly the same value as 1.414. It is less tidy, but it means the same thing.
The obvious question here is 'why does it matter'? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 10, 2007 10:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think the issue is that the message is being changed by being read into a logical message tree, and then written out from the logical message tree.
I suppose one way to avoid this is to read the message as BLOB, parse it into a throwaway tree, and then pass the same BLOB back out.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Sep 10, 2007 1:31 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I think the issue is that the message is being changed by being read into a logical message tree, and then written out from the logical message tree. |
If you convert a value from its lexical form to some data type ( xs:double in this case ) then you often lose information about its original lexical format. So this problem would also occur with float values like '1.2000' or an integer written as '0001'. If that's a problem, there is a simple workaround - change it to xs:string.
I realise that in an ideal world, the output format would always look identical to the input format unless the field was changed. That could be achieved, but it would have quite a large impact on performance. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Sep 10, 2007 2:06 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Sure, I agree with that.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
