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 » DFDL parsing issue in IB 9.0.0.4

Post new topic  Reply to topic Goto page Previous  1, 2, 3
 DFDL parsing issue in IB 9.0.0.4 « View previous topic :: View next topic » 
Author Message
timber
PostPosted: Wed May 25, 2016 12:43 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

Quote:
when i compile in version 8.0.0.6 toolkit and deploy in 9.0.0.5 broker it is working.
I don't understand that comment.

A DFDL schema is not 'compiled' by the toolkit when the BAR file is created. It is compiled by the runtime as part of the deploy. The BAR file builder simply zips the XSDs into a single file and puts them into the BAR file.

Please explain in detail what tests you have conducted. And please check carefully that you are using *exactly* the same schemas and input messages in both tests.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed May 25, 2016 3:55 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

And please put further data/code/schemas/traces/etc in [ c o d e ] blocks.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
rsk33
PostPosted: Thu May 26, 2016 1:43 am    Post subject: Reply with quote

Centurion

Joined: 21 Aug 2006
Posts: 141

what i meant building the application..

I have solved the issue by changing the encoding. where ever the fields were stopping in the DFDL test parser, i changed the encoding US-ASCII to UTF-8.

In version 8.0.0.6 the working DFDL encoding was US-ASCII.

i simulated a DFDL model consist of complexfield in which a field1 having minoccurs=0 and maxoccurs =unbounded and occurscountkind =implicit. see the message below. it is not working. but when i put the field1 under sequence and defined terminator ';', it is working fine. of course i checked/changed encoding and tested.

Is this correct behavior of DFDL ...


message[complexfield[field1[11],field1[22],field2[33]]]


message[complexfield[field1[11],field1[22];,field2[33]]]
Back to top
View user's profile Send private message
timber
PostPosted: Thu May 26, 2016 6:18 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

Quote:
where ever the fields were stopping in the DFDL test parser, i changed the encoding US-ASCII to UTF-8
Do you mean that you changed the encoding on the individual fields?

Quote:
i simulated a DFDL model consist of complexfield in which a field1 having minoccurs=0 and maxoccurs =unbounded and occurscountkind =implicit. see the message below. it is not working
If you quoted the error message we might have a small chance of telling you what the problem was

Quote:
Is this correct behavior of DFDL
Based on the information that you have supplied, nobody could possibly answer that question. If you need an answer, please start a new thread and include all of the relevant information.
Back to top
View user's profile Send private message
rsk33
PostPosted: Thu May 26, 2016 8:31 am    Post subject: Reply with quote

Centurion

Joined: 21 Aug 2006
Posts: 141

yes i have changed the individual fields encoding.
as i told you the parser was not showing in the trace any error in dfdl parser test. i understand it is very difficult without any clue.

i highly appreciate your effort and wonderful support in the forum..
thanks a bunch..

would please answer my other question/example i gave in my previous message.
Back to top
View user's profile Send private message
rsk33
PostPosted: Thu May 26, 2016 8:34 am    Post subject: Reply with quote

Centurion

Joined: 21 Aug 2006
Posts: 141

i will open a new thread for my other question..
Back to top
View user's profile Send private message
timber
PostPosted: Thu May 26, 2016 12:56 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

Quote:
yes i have changed the individual fields encoding
Are you really claiming that the sender has encoded most of the message using US-ASCII, but it has encoded a few of the fields as UTF-8?
Back to top
View user's profile Send private message
rsk33
PostPosted: Thu May 26, 2016 10:26 pm    Post subject: Reply with quote

Centurion

Joined: 21 Aug 2006
Posts: 141

yes, i have changed the encoding few of the fields where ever it was stopped in the dfdl trace and not showing any error.

originally it was US-ASCII..
Back to top
View user's profile Send private message
shanson
PostPosted: Fri Jun 03, 2016 1:48 am    Post subject: Reply with quote

Partisan

Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley

That does not explain why it worked in v8 and not in v9.
Back to top
View user's profile Send private message
timber
PostPosted: Fri Jun 03, 2016 11:59 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

The explanation may lie here:
Quote:
In version 8.0.0.6 the working DFDL encoding was US-ASCII.
I'm not sure exactly what the OP meant, but it sounds as if the test setup was not identical in the two systems.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3 Page 3 of 3

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » DFDL parsing issue in IB 9.0.0.4
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.