| Author |
Message
|
| timber |
 Posted: Wed May 25, 2016 12:43 am Post subject: |
 |
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| 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 |
|
 |
| mqjeff |
| Posted: Wed May 25, 2016 3:55 am Post subject: |
|
|
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 |
|
|
| rsk33 |
| Posted: Thu May 26, 2016 1:43 am Post subject: |
|
|
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 |
|
|
| timber |
| Posted: Thu May 26, 2016 6:18 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| 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 |
|
|
| rsk33 |
| Posted: Thu May 26, 2016 8:31 am Post subject: |
|
|
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 |
|
|
| rsk33 |
| Posted: Thu May 26, 2016 8:34 am Post subject: |
|
|
Centurion
Joined: 21 Aug 2006
Posts: 141
|
| i will open a new thread for my other question.. |
|
| Back to top |
|
|
| timber |
| Posted: Thu May 26, 2016 12:56 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| 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 |
|
|
| rsk33 |
| Posted: Thu May 26, 2016 10:26 pm Post subject: |
|
|
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 |
|
|
| shanson |
| Posted: Fri Jun 03, 2016 1:48 am Post subject: |
|
|
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 |
|
|
| timber |
| Posted: Fri Jun 03, 2016 11:59 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
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 |
|
|
|
|
