| Author |
Message |
 Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Fri Feb 27, 2015 10:02 am Subject: Nil for End of Stream in DFDL Model |
| Changing lengthKind from 'prefixed' to 'implicit' and setting min/max occurrence 0/1 does violate ISO8583 standard but it will do the job for the time being.I don't see how that fixes the problem. Wha ... |
| Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Feb 25, 2015 10:47 am Subject: Nil for End of Stream in DFDL Model |
| Looks like setting min/max occurrence to 0/1 and setting occurrence kind to implicit does also parse message and does not terminates connection on TCPIPServerInput node. Our IBM consultant also sugge ... |
| Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Feb 25, 2015 6:40 am Subject: Nil for End of Stream in DFDL Model |
Did you define the last 2 fields as being optional? (occurs 0 to 1) with occurs count kind to implicit ? 
Sorry i overlooked your suggestion. Looks like setting min/max occurrence to 0/1 ... |
| Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Feb 25, 2015 5:37 am Subject: Nil for End of Stream in DFDL Model |
| Firstly, if a field is missing entirely, you can not have it appear as nil. The DFDL spec makes a clear distinction between a field being missing and having a representation. A field can be treated as ... |
| Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Feb 25, 2015 4:00 am Subject: Nil for End of Stream in DFDL Model |
Your format sounds very similar to ISO8583, which also has bits at the start of the message to indicate which fields are present. It also has many fields with prefixed lengths.
The DFDL schemas fo ... |
| Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 24, 2015 11:08 pm Subject: Nil for End of Stream in DFDL Model |
Did you define the last 2 fields as being optional? (occurs 0 to 1) with occurs count kind to implicit ?
Yes the last 2 fields can be optional but occurrence count kind is expression not ... |
| Topic: Extra xsi element after Mapping and DFDL nil value for EOS |
aslam_kumhar
Replies: 8
Views: 5155
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 24, 2015 10:33 am Subject: Extra xsi element after Mapping and DFDL nil value for EOS |
If the prefixed-length element is a complex element then you cannot ( in any version of IIB up to v9.0.0.2 ) parse it as a nil value.
If it is simple then you can.
element is of simple type not c ... |
| Topic: Nil for End of Stream in DFDL Model |
aslam_kumhar
Replies: 11
Views: 8798
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 24, 2015 10:30 am Subject: Nil for End of Stream in DFDL Model |
Hi Everyone,
We are having following issues.
1. Parsing messages with last element missing whose properties are such that occurence kind is '1' based on expression and lengthKind is 'pref ... |
| Topic: Extra xsi element after Mapping and DFDL nil value for EOS |
aslam_kumhar
Replies: 8
Views: 5155
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Feb 09, 2015 8:20 am Subject: Extra xsi element after Mapping and DFDL nil value for EOS |
If the prefixed-length element is a complex element then you cannot ( in any version of IIB up to v9.0.0.2 ) parse it as a nil value.
If it is simple then you can.
element is of simple type not c ... |
| Topic: Extra xsi element after Mapping and DFDL nil value for EOS |
aslam_kumhar
Replies: 8
Views: 5155
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Feb 07, 2015 7:41 am Subject: Extra xsi element after Mapping and DFDL nil value for EOS |
I don't know why that is happening, but I suggest that you adjust your ESQL so that it ignores any element that is in the xsi namespace.
Fair enough, I will deal with it in ESQL.
That's bot ... |
| Topic: Extra xsi element after Mapping and DFDL nil value for EOS |
aslam_kumhar
Replies: 8
Views: 5155
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat Feb 07, 2015 2:35 am Subject: Extra xsi element after Mapping and DFDL nil value for EOS |
| Guys any help will be really appreciated. |
| Topic: Extra xsi element after Mapping and DFDL nil value for EOS |
aslam_kumhar
Replies: 8
Views: 5155
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 05, 2015 4:56 am Subject: Extra xsi element after Mapping and DFDL nil value for EOS |
Sorry for replying late.
The xsi:type attribute is for use by XML processors. DFDL should ignore it. Is it actually causing a problem?
yes my message format is iso8583 and after mapping i gene ... |
| Topic: Extra xsi element after Mapping and DFDL nil value for EOS |
aslam_kumhar
Replies: 8
Views: 5155
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Feb 02, 2015 11:25 pm Subject: Extra xsi element after Mapping and DFDL nil value for EOS |
Hi Everyone,
I don't know the exact reason behind this but sometimes there's an extra element named "http://www.w3.org/2000/xmlns/:xsi " with value "http://www.w3.org/20 ... |
| Topic: Log4j brokerlog.xml Classpath Issue |
aslam_kumhar
Replies: 11
Views: 18297
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jan 22, 2015 7:12 am Subject: Log4j brokerlog.xml Classpath Issue |
| It will do the job, but just to be clear I just wanted to say that it would be better to use Userdefined Configurable Service to retrieve properties in Transformation Nodes for someone like me who did ... |
| Topic: Log4j brokerlog.xml Classpath Issue |
aslam_kumhar
Replies: 11
Views: 18297
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jan 22, 2015 6:21 am Subject: Log4j brokerlog.xml Classpath Issue |
I don't think you follow. You don't need to code the path where the jar file is at all - you let the system find it in the classpath (which is automatic).
Put the jar file in one of the shared-clas ... |
