Author |
Message |
Topic: DFDL parsing error when first array item is empty string |
shanson
Replies: 9 Views: 8474
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 07, 2016 12:25 am Subject: DFDL parsing error when first array item is empty string |
Raise a PMR for the error. You have shown it's been fixed in v10 so there must be a fix that can be ported to v8.
If you are modelling recA etc as nillable then I think you are stuck with the side- ... |
Topic: DFDL parsing error when first array item is empty string |
shanson
Replies: 9 Views: 8474
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Nov 04, 2016 1:30 am Subject: DFDL parsing error when first array item is empty string |
The problem is that the '|' may mean something different at a lower level in the model. The DFDL parser can't assume that it is the next separator at the current level. So it descends into the sequenc ... |
Topic: DFDL parsing error when first array item is empty string |
shanson
Replies: 9 Views: 8474
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Nov 03, 2016 4:07 am Subject: DFDL parsing error when first array item is empty string |
You have defined all your elements as nillable="true" with dfdl:nilValue as the empty string. For your example, that causes the parser to assign <nil> to recA[1].
Not sure why an em ... |
Topic: DFDL parser- String fields has Space or low-Value |
shanson
Replies: 23 Views: 21047
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 14, 2016 12:12 am Subject: DFDL parser- String fields has Space or low-Value |
I think we now have all the facts.
- You have some fields that, when nil, are entirely filled with low-values. You should model those with nilKind='literalCharacter' and nilValue='%#r00'
- You have ... |
Topic: DFDL parser - getting weird character |
shanson
Replies: 4 Views: 4029
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 12, 2016 7:59 am Subject: DFDL parser - getting weird character |
The DFDL editor test parse/serialize views in the IIB toolkit let you see the hex. On the toolbar for those views, click on the upside-down triangle symbol and select 'Show hex'. |
Topic: DFDL parser- String fields has Space or low-Value |
shanson
Replies: 23 Views: 21047
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Sep 09, 2016 3:58 am Subject: DFDL parser- String fields has Space or low-Value |
I claim that that your schema should produce a schema definition error unless length="1" and lengthUnits="bytes", because the nilValue is too short to be a valid value for the fie ... |
Topic: DFDL parser- String fields has Space or low-Value |
shanson
Replies: 23 Views: 21047
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 07, 2016 11:29 pm Subject: DFDL parser- String fields has Space or low-Value |
It sounds like incorrect DFDL annotations for the 2-3 fields that are not working. Please supply the snippet of DFDL schema that covers those fields. |
Topic: DFDL parsing csv file error |
shanson
Replies: 12 Views: 9053
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 07, 2016 9:32 am Subject: DFDL parsing csv file error |
Perhaps the A, B, and Z records could be removed from the choice, and modeled as records that do not repeat
That's how I would do it. The choice model is flexible but if you want strict validation ... |
Topic: PATTERN DOWNLOAD AVAILABLE: MATIP Processing |
shanson
Replies: 5 Views: 8602
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Aug 29, 2016 11:48 pm Subject: PATTERN DOWNLOAD AVAILABLE: MATIP Processing |
It's never been officially upgraded to work with v9 and v10. I believe the issue is with running the pattern, not the generated artifacts. You could install v7 toolkit and import the pattern, then mi ... |
Topic: Dfdl |
shanson
Replies: 2 Views: 2181
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2016 7:39 am Subject: Dfdl |
If you want a single DFDL model for all 4 formats, you can do that. Model the content as a choice, and if the content does not start with an initiator, try using a DFDL discriminator to distinguish be ... |
Topic: what is difference between message set & message model |
shanson
Replies: 11 Views: 14852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2016 7:35 am Subject: what is difference between message set & message model |
A 'message model' is the generic term for an IIB artifact that describe a set of message formats. There are two kinds of message model - the original kind called a 'message set' and the newer kind ( ... |
Topic: Healthcare Pack - Truncating fields with subfields |
shanson
Replies: 8 Views: 5936
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2016 7:07 am Subject: Healthcare Pack - Truncating fields with subfields |
You can make a structure fixed length using dfdl:lengthKind 'explicit' but an attempt to serialize the structure which exceeds the length will give a processing error. You can only truncate fixed leng ... |
Topic: Healthcare Pack - Truncating fields with subfields |
shanson
Replies: 8 Views: 5936
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2016 5:43 am Subject: Healthcare Pack - Truncating fields with subfields |
Truncating structures is not supported by DFDL, it's a inherently dangerous thing to do as you can render the message impossible to re-parse. Truncation of string elements that are defined with a spec ... |
Topic: Delimited Messages Parsing |
shanson
Replies: 6 Views: 5245
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2016 2:29 am Subject: Delimited Messages Parsing |
I assume you are using WMB v7 as your solution is using MRM and not DFDL. If I recall there is a check box for 'All Elements Delimited' that gets MRM to lokk at the length. Alternatively set max lengt ... |
Topic: Parsing select columns from a CSV |
shanson
Replies: 11 Views: 9458
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Aug 25, 2016 2:27 am Subject: Parsing select columns from a CSV |
DFDL can not assign element names dynamically. It always uses the element name declared in the schema. |