| Author |
Message
|
| pchalla |
 Posted: Fri Feb 19, 2016 8:09 am Post subject: ERROR CODE : "CTDV1111E" IN IIB 10 DFDL |
 |
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
Hi all,
I created a message model with 'Other Xml' format. But in the DFDL editor it is throwing an error with code "CTDV1111E".
CTDV1111E : When representation is text, DFDL property 'textBidi' must be set. Element: #xmlns(p="http://xxx")xscd(/schemaElement::p:ElementName). xxx.xsd.
But in the DFDL editor properties tab I couldn't find the 'textBidirectional' property.
Is there any one with this kind of issue. Help please.....
Thanks in advance. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Feb 19, 2016 8:31 am Post subject: Re: ERROR CODE : "CTDV1111E" IN IIB 10 DFDL |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| pchalla wrote: |
Hi all,
I created a message model with 'Other Xml' format. But in the DFDL editor it is throwing an error with code "CTDV1111E".
CTDV1111E : When representation is text, DFDL property 'textBidi' must be set. Element: #xmlns(p="http://xxx")xscd(/schemaElement::p:ElementName). xxx.xsd.
But in the DFDL editor properties tab I couldn't find the 'textBidirectional' property.
Is there any one with this kind of issue. Help please.....
Thanks in advance. |
I'd say your message model has the wrong format...
Should you not have started with the DFDL wizard ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pchalla |
| Posted: Fri Feb 19, 2016 8:37 am Post subject: |
|
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
Hi, thanks for your reply.
As I selected 'Other Xml' format while creating the message model, it took me to Xml Schema Editor. Then I opened it with DFDL editor.
Is there any thing wrong in doing so? |
|
| Back to top |
|
|
| pchalla |
| Posted: Fri Feb 19, 2016 8:41 am Post subject: |
|
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
| After opening it with the DFDL editor, it is showing a warning to add a default format. After adding the default it is throwing all the errors |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 19, 2016 8:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
... what makes it an "Other XML"? Is it not described by a straightforward schema?
Not sure why you would use DFDL to explicitly parse XML data.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| pchalla |
| Posted: Fri Feb 19, 2016 9:25 am Post subject: |
|
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
I am creating a message model in a library. The global elements created in this message model will be referred by another message model.
No, it is not described by a straightforward schema. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 19, 2016 9:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| pchalla wrote: |
I am creating a message model in a library. The global elements created in this message model will be referred by another message model.
No, it is not described by a straightforward schema. |
Is it describable in any way by a standard XSD? (straightforward or not)?
Are you having to extract multiple XML documents from a single input message?
You might look at using DFDL to describe only the non-XML parts, leaving the XML parts as blobs. Then use the XMLNSC parser inside the message flow to process the actual data.
Using DFDL to process XML data smells like a bad idea to me. Your situation might actually require it, but...
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| pchalla |
| Posted: Fri Feb 19, 2016 9:57 am Post subject: |
|
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
We can set the properties of the 'default format' and can refer to it.
But, even in this properties tab I couldn't find the 'textBidi' property. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 19, 2016 10:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
My advice: discard this xml and start with the DFDL wizard.
Do not use the DFDL UI to browse a non DFDL xsd. Pain comes that way...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 19, 2016 10:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| pchalla |
| Posted: Fri Feb 19, 2016 10:22 am Post subject: |
|
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
| If it is not supported,then what will be the other way of doing this? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 19, 2016 10:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| pchalla wrote: |
| If it is not supported,then what will be the other way of doing this? |
What exactly are you trying to do? Explain the problem and we might be able to point you in the direction of a solution...
_________________
MQ & Broker admin
Last edited by fjb_saper on Fri Feb 19, 2016 10:27 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 19, 2016 10:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Modify your DFDL to not parse the relevant elements as text - treat them as blobs instead.
Again, though. You really shouldn't be using DFDL to parse data that is actually XML. You should find ways to use DFDL to isolate the XML data and then parse that using XMLNSC.
Can you describe your format enough to indicate why you are using DFDL?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| pchalla |
| Posted: Sat Feb 20, 2016 4:55 pm Post subject: |
|
|
Novice
Joined: 15 Jan 2016
Posts: 10
|
fjb_saper, My issue actually is...
My input is 'CSV' and the output is 'XML', before sending it to output we are validating it against an xml schema to make sure if we are building the exact message and populating the values needed by the next flow.
I created a DFDL for input 'CSV' and the 'XML' schema for validation in a shared library-1. But there is another shared library-2 which contains elements which are used by all applications including the sharedlibrary-2.
I created the elements in the shared library-2 with 'Other XML' format.
Now am not able to refer to those shared library-2 elements from the 'CSV' DFDL in sharedlibrary-1.
As i created one message model with 'CSV' and other with 'OtherXML', how can i refer 'XML' schema from 'CSV' DFDL?
Help me please...  , Thanks |
|
| Back to top |
|
|
| timber |
| Posted: Sun Feb 21, 2016 11:56 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| I created a DFDL for input 'CSV' and the 'XML' schema for validation in a shared library-1. |
I assume that the structure of the output XML is different from the structure of the input CSV? Because if they were the same then you could use the DFDL schema to validate the output XML.
| Quote: |
| there is another shared library-2 which contains elements which are used by all applications including the sharedlibrary-2. |
That may be OK...if you are sure that these elements will not require any DFDL annotations. However...
| Quote: |
Now am not able to refer to those shared library-2 elements from the 'CSV' DFDL in sharedlibrary-1.
As i created one message model with 'CSV' and other with 'OtherXML', how can i refer 'XML' schema from 'CSV' DFDL? |
First, you need to ignore the 'CSV' versus 'Other XML...' distinction. A DFDL schema is 'just a schema'. It follows all of the rules of the XSD language, including xs:include and xs:import. I cannot find any guidance in the Knowledge Center on how to reference an xsd in another shared library. But it sounds as if it should be possible. What have you tried so far? |
|
| Back to top |
|
|
|
|
