| Author |
Message |
 Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 24, 2012 7:33 am Subject: DFDL delimited empty string element |
For the benefit of others . . .
Although this did help to properly parse the example I provided for this forum, it does not work for the real message model and associated data. The element padded ... |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue May 22, 2012 11:10 am Subject: DFDL delimited empty string element |
| I opened a PMR (03659 442 000) last week that was forwarded to L3 and haven't had anyone contact me yet on it. The only way I've been able to get this to parse correctly is to change the spaces to ch ... |
| Topic: WMB 8 Windows Oracle ODBC issue |
msnyder
Replies: 13
Views: 7759
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 18, 2012 9:04 am Subject: WMB 8 Windows Oracle ODBC issue |
| You'll need to open a PMR to get the fixes or wait until the 1st fix pack becomes available which should be very soon. |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 18, 2012 6:26 am Subject: DFDL delimited empty string element |
| Yes, it was separatorPolicy="suppressed" and I changed it to separatorPolicy="suppressedAtEndLax" with the same results. |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 18, 2012 5:33 am Subject: DFDL delimited empty string element |
Yes, one of the best parts of the DFDL functionality in WMB is the test parser. Unfortunately, I can't post my actual message model and didn't have enough time to create a simple example yesterday.
... |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 17, 2012 12:46 pm Subject: DFDL delimited empty string element |
I have hit another issue with this using the definitions above. For input like:
element1|2 |element3|element4
The 2nd element is being parsed as '2' instead of '2 ' with parsing continu ... |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 17, 2012 10:53 am Subject: DFDL delimited empty string element |
Besides my obvious type problem in the previous post, I had to add dfdl:useNilForDefault="yes" for it to work
<xsd:complexType name="recordType">
<xsd:sequen ... |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 17, 2012 6:59 am Subject: DFDL delimited empty string element |
I even created a new workspace which helped get rid of the variable length text element issue I had 2 weeks ago and still am getting the same exact exception.
<?xml version="1.0" encod ... |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 17, 2012 4:17 am Subject: DFDL delimited empty string element |
Unfortunately, the combination recommended along with various others I tried earlier result in the same exception. I'll open a PMR to get the fix.
Also, has any date been set for fix pack 1? Than ... |
| Topic: DFDL delimited empty string element |
msnyder
Replies: 22
Views: 22768
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 16, 2012 4:54 pm Subject: DFDL delimited empty string element |
| Need a little help understanding if this is a bug or just not defined properly.<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:dfdl="http://www.og ... |
| Topic: DFDL hex initiators |
msnyder
Replies: 6
Views: 4030
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 10, 2012 7:04 am Subject: DFDL hex initiators |
| Yes I noticed that it was backwards. However, I had added another byte to the mix and miskeyed it. After changing, it worked like a charm. Thanks for your help. |
| Topic: DFDL hex initiators |
msnyder
Replies: 6
Views: 4030
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 10, 2012 5:52 am Subject: DFDL hex initiators |
| After further review, I tried it like"%#r1104;" and got the aforementioned exception. According to the spec, 1 or more pairs is acceptable. However, after separating into 2, the exception ... |
| Topic: DFDL hex initiators |
msnyder
Replies: 6
Views: 4030
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 10, 2012 5:45 am Subject: DFDL hex initiators |
| Yes, I tried that but got an exception saying something to the effect that it is not supported in the IBM implementation. |
| Topic: DFDL hex initiators |
msnyder
Replies: 6
Views: 4030
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 10, 2012 5:21 am Subject: DFDL hex initiators |
| I have a situation where record types are identified by 2 byte little endian integers. The parser is not finding a choice branch when the initiator is specified as a hex value, e.g. dfdl:initiator=&q ... |
| Topic: DFDL variable length string |
msnyder
Replies: 12
Views: 6479
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 10, 2012 5:10 am Subject: DFDL variable length string |
| The issue was a result of a corrupted workspace. After creating a new workspace and changing all variable length references to relative paths, the variable length array data elements parsed without i ... |
