| Author |
Message
|
| zhumingvictor |
 Posted: Fri Jun 28, 2013 4:59 am Post subject: |
 |
|
Novice
Joined: 10 May 2013
Posts: 17
|
| Anybody found a solution for this? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Jun 28, 2013 5:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhumingvictor wrote: |
| Anybody found a solution for this? |
Solution to what? Unless you describe your problem we can't know if it's actually the same problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zhumingvictor |
| Posted: Fri Jun 28, 2013 5:41 am Post subject: |
|
|
Novice
Joined: 10 May 2013
Posts: 17
|
| Vitor wrote: |
| zhumingvictor wrote: |
| Anybody found a solution for this? |
Solution to what? Unless you describe your problem we can't know if it's actually the same problem. |
Solution for the exact same problem this thread talked about. Actually I just found something new, I tried to parse the DFDL and debug, it will throw error only before continue to the next node. Before that if I inspect the tree in debug it looks fine. Then I tried another way, I assigned everything under parsed DFDL to part of the output root node then delete the original DFDL node it will pass but only pass in Debug mode. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 28, 2013 5:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Using debug changes the way the message tree is handled. Take a user trace instead.
If it's the same problem as this, follow the same advice as this thread & raise a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zhumingvictor |
| Posted: Fri Jun 28, 2013 5:48 am Post subject: |
|
|
Novice
Joined: 10 May 2013
Posts: 17
|
| Vitor wrote: |
Using debug changes the way the message tree is handled. Take a user trace instead.
If it's the same problem as this, follow the same advice as this thread & raise a PMR. |
But it will work if I step line by line through the parse and delete code, if I only put a break point after it erorr occur.
Insert
Type:INTEGER:5
Text:CHARACTER:CTDP3000E: Unexpected end of data at byte offset '<MISSING INSERT 0>' while parsing element '<MISSING INSERT 1>'. The parser encountered the end of the data stream or the end of a parent element. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jul 01, 2013 12:49 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
@zhumingvictor: There was a problem in this area, and it was fixed in v8.0.0.2. Which version are you using?
Vitor said:
| Quote: |
| Using debug changes the way the message tree is handled. |
Hmmm. That used to be true, but it was fixed in one of the later v6.1 CSDs. The v8 debugger should not change message flow behaviour.
| Quote: |
| Take a user trace instead. |
User trace is very useful. So is the debugger. They show you different things. In this situation, it sounds as if user trace would be an excellent choice. |
|
| Back to top |
|
|
|
|
