I cannot offer a definite solution/diagnosis but a few hard facts will probably help to eliminate some lines of investigation....
- You definitely can output unordered data in CWF when you set Composition to Unordered Set. Performance will suffer a little because the parser has to shuffle the elements into the correct order as it outputs them.
- Setting Validation to 'Content and Value' is a good technique for finding tree/model mismatches. You can switch if off again before going into production.
- The error message 'Unknown or Invalide Type found in Tree' sounds like a known defect in the product. See http://www-1.ibm.com/support/docview.wss?uid=swg1IY88105. Looks as if you may need to upgrade to at least FP3 ( but FP is the latest and greatest ).
Joined: 03 Aug 2006 Posts: 16 Location: Campinas/SP - Brazil
SOLVED!!!!
Thanks for all replies.
I just had to change my "Encoding Null" property from "NullLiteralFill" to "NullPadFill". _________________ IBM Certified Solution Developer - WebSphere Message Broker V6.0
Joined: 03 Aug 2006 Posts: 16 Location: Campinas/SP - Brazil
kimbert wrote:
Can you quote the errors please.
The parser was skipping cpf field. So, the characters that was from cpf field were parsed in the next field. Then, all message from this point forward was wrong. _________________ IBM Certified Solution Developer - WebSphere Message Broker V6.0
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