| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| error shown after deploying! |
« View previous topic :: View next topic » |
| Author |
Message
|
| prabhu_chn |
 Posted: Mon Jun 21, 2004 1:22 pm Post subject: error shown after deploying! |
 |
|
Newbie
Joined: 20 May 2004
Posts: 7
|
hi,
Iam trying to convert a message from CWF to TDS format. when I tried deploying it gave me a error....
BIP1836E: The create wire format descriptor operation has not completed successfully.
The create wire format descriptor operation encountered one or more errors. A report file, (MRMP_MS3_TDS.log), has been created in C:/Program Files/IBM/WebSphere MQ Integrator 2.1/log/ on the Configuration Managers machine.
See the MRMP_MS3_TDS.log file for details of the error.
when i checked with the log file ...
Beginning Validation..
Validating Project
Validating Types
ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of simple type Binary must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: PaxTitle)
(Type ID: PaxData3_TYPE)
Return Code: -80
ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of simple type Binary must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: PaxBaggageAllowance)
(Type ID: PaxData3_TYPE)
Return Code: -80
Validating Messages
Trace Info
===========
EXCEPTION: TDSValidator::Validate:
TDS Validation failed.
2 errors
0 warnings
Return Code: -1
Iam Unable to trace this error .
can anyone help me solving this problem........
thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jun 21, 2004 1:37 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The error messages you posted tell you exactly what needs to be fixed.
The element PaxTitle must have a Length or Length reference defined for it.
Similarly, the element PaxBaggageAllowance must have a length or length reference defined.
Both of these elements exist within PaxData3_TYPE. I suspect that this is defined as a fixed-length type or a fixed-elements delimited type, and you haven't given a length for these two elements.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prabhu_chn |
| Posted: Mon Jun 21, 2004 2:17 pm Post subject: |
|
|
Newbie
Joined: 20 May 2004
Posts: 7
|
thanks jeff,
that would be of great help |
|
| Back to top |
|
|
| shanson |
| Posted: Tue Jun 22, 2004 12:42 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
Fyi - in V2 due to the way this code was historically written, the time that your MRM message model is checked for correctness varies, depending on the physical formats you are using. Your CWF and XML formats get checked when you check-in objects into the message set, but much of the TDS format checking does not take place until deploy time.
In V5 this inconsistency goes away - all checking is performed when you save the message definition file using CTRL-S. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
