ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » New DFDL Parser Errors in WMB 8.0.0.4 not in WMB 8.0.0.2

Post new topic  Reply to topic
 New DFDL Parser Errors in WMB 8.0.0.4 not in WMB 8.0.0.2 « View previous topic :: View next topic » 
Author Message
EricCox
PostPosted: Fri Nov 14, 2014 12:25 pm    Post subject: New DFDL Parser Errors in WMB 8.0.0.4 not in WMB 8.0.0.2 Reply with quote

Master

Joined: 08 Apr 2011
Posts: 292

To all,

Does anyone know why we are now experiencing new DFDL parser errors in WMB 8.0.0.4? We upgraded two of our Development Brokers to 8.0.0.4 from 8.0.0.2 and are now getting this error.

BIP5807E: The DFDL parser signalled that a processing error occurred. The message from the DFDL parser is: 'CTDP3043E: Text to number conversion error for string ' '. Character '' at offset '1' cannot be parsed.'

Was this a defect in 8.0.0.2 and it is fixed in 8.0.0.4? In 8.0.0.2 an application sends us a space ' ' in a field that is defined as numeric in the DFDL but we don't get a parsing error. Now is it possible they fixed that and the DFDL parser is now enforcing the correct data type for the field? Thus, it is now, as the error above states cannot interpret a ' ' as a valid numeric value?

Also, is there a setting in the DFDL Message Model that will allow that if there is data it will enforce the numeric data type otherwise ignore the lack of data?

Or is this a defect in 8.0.0.4?

Thanks,
Eric
Back to top
View user's profile Send private message
kimbert
PostPosted: Sun Nov 16, 2014 2:40 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Well, a space is never a valid value for a numeric field. My guess is that a defect was fixed in the DFDL parser. What value do you expect the DFDL parser to assign to this 'number'?

If you do need to treat one ( or more ) spaces as a valid value for an xs:integer field then you should
- set the element to be 'nillable'
- set the nil kind to 'Nil Literal Character'
- set the nil value to %SP;
...which will cause one or more spaces to be interpret as a NULL value. In your code, you can test for a NULL and translate it to whatever value you need.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too.
Back to top
View user's profile Send private message
EricCox
PostPosted: Mon Nov 17, 2014 9:22 am    Post subject: Spot On Reply with quote

Master

Joined: 08 Apr 2011
Posts: 292

Kimbert,
Upon initial testing you seem to be spot on. We do actually want to interpret this space as nil. Then when mapped to XML output it should produce an empty XML tag. That is precisely what we want at this time.
Thanks much.
I'm still confirming the fix with IBM. They are making me work to confirm what they did with the DFDL paser though. Geez!
Thanks,
Eric
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » New DFDL Parser Errors in WMB 8.0.0.4 not in WMB 8.0.0.2
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.