I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

Hi Parul,

Can you check if the static library is referenced in your application? If that is not the case the dfdl will not show up. 

   -->

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

Thanks for the checking Francis.

Yes, I have given the reference of the static lib to my application. The suspect thing is the XSD I'm taking is working for MRM format. Is the same will work for DFDL domain as well? Or we need some changes to be implemented for DFDL XSD files?

Hi Parul,

Can you check if the static library is referenced in your application? If that is not the case the dfdl will not show up. 

   -->

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

Hi Parul

If I'm not mistaken, Message Sets (MRM) have been deprecated (deprecated, not removed) from v11 onward. Message Models (DFDL) are the way forward.

A Message Set that has been created specifically for MRM can't be reused as is for DFDL, you will need to create a new DFDL Message Model.

I have created a static library (Btw, have a look at shared libraries, they are better - unless you have a very specific need for maintaining schema's per application) that contains both an mrm and dfdl entry

And they are not cross-compatible

If you want to use the DFDL parses, you need to create a DFDL Message Model.

If I am completely missing the ball here, and you are trying to do something else, please let me know. And maybe share your code and/or application/library setup.

Thanks for the checking Francis.

Yes, I have given the reference of the static lib to my application. The suspect thing is the XSD I'm taking is working for MRM format. Is the same will work for DFDL domain as well? Or we need some changes to be implemented for DFDL XSD files?

Hi Parul,

Can you check if the static library is referenced in your application? If that is not the case the dfdl will not show up. 

   -->

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

Thanks for the reply. 

So, here is the story:

We are upgrading our application from WMB v7 to ACE 13.. In WMB v7 we are using Message sets for incoming MRM format messages. So as you said MRM is getting deprecated, we are planning to change the MRM(Message Set thing) to DFDL Modelling. What I have is XSDs of the Message Sets we are using in version 7. Now, in ACE 13 I have created a DFDL model under one static Lib and using the old Schema(XSD schema we have for MRM) for it:

So, my question is will the old XSD will work or I need to create a DFDL schema from scratch for each WMB interfaces?

Or is there any way I can create a DFDL schema from XML Schema.

------------------------------
Parul Awad

Original Message:
Sent: Fri June 13, 2025 09:04 AM
From: Matthias Blomme
Subject: DFDL Message selection is coming blank

Hi Parul

If I'm not mistaken, Message Sets (MRM) have been deprecated (deprecated, not removed) from v11 onward. Message Models (DFDL) are the way forward.

A Message Set that has been created specifically for MRM can't be reused as is for DFDL, you will need to create a new DFDL Message Model.

I have created a static library (Btw, have a look at shared libraries, they are better - unless you have a very specific need for maintaining schema's per application) that contains both an mrm and dfdl entry

And they are not cross-compatible

If you want to use the DFDL parses, you need to create a DFDL Message Model.

If I am completely missing the ball here, and you are trying to do something else, please let me know. And maybe share your code and/or application/library setup.

------------------------------
Regards
Matthias Blomme
Integration Specialist
Integration Designers
Turnhout

Original Message:
Sent: Fri June 13, 2025 08:32 AM
From: Parul Awad
Subject: DFDL Message selection is coming blank

Thanks for the checking Francis.

Yes, I have given the reference of the static lib to my application. The suspect thing is the XSD I'm taking is working for MRM format. Is the same will work for DFDL domain as well? Or we need some changes to be implemented for DFDL XSD files?

------------------------------
Parul Awad

Original Message:
Sent: Fri June 13, 2025 07:55 AM
From: Francis Cocx
Subject: DFDL Message selection is coming blank

Hi Parul,

Can you check if the static library is referenced in your application? If that is not the case the dfdl will not show up. 

   -->

------------------------------
Francis Cocx

Original Message:
Sent: Thu June 12, 2025 03:06 AM
From: Parul Awad
Subject: DFDL Message selection is coming blank

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

------------------------------
Parul Awad
------------------------------

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

Hi everyone,

I've created a static library where I've implemented message modeling using DFDL to XML Schema. For input, I'm using an MQ Input node, and in the node's properties, I've selected the DFDL message domain for parsing the input message.

The XML schema itself is valid-I've already tested and confirmed it separately. However, when I try to browse the message, the output appears blank, and no parsing errors are shown either.

This issue is blocking further development for a project that also supports a daycare near me integration feature, where message accuracy is critical for syncing child enrollment data.

Has anyone encountered a similar issue with DFDL message domains returning empty payloads despite valid schemas? Could this be related to the DFDL schema root, input data format, or missing properties?

Any help or pointers would be appreciated. Thanks in advance!

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

Hi everyone,

I've created a static library where I've implemented message modeling using DFDL to XML Schema. For input, I'm using an MQ Input node, and in the node's properties, I've selected the DFDL message domain for parsing the input message.

The XML schema itself is valid-I've already tested and confirmed it separately. However, when I try to browse the message, the output appears blank, and no parsing errors are shown either.

This issue is blocking further development for a project that also supports a daycare near me integration feature, where message accuracy is critical for syncing child enrollment data.

Has anyone encountered a similar issue with DFDL message domains returning empty payloads despite valid schemas? Could this be related to the DFDL schema root, input data format, or missing properties?

Any help or pointers would be appreciated. Thanks in advance!

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).

I have created a static library where I have created a Message Modelling (DFDL -> XML Schema). As an input I have MQ input node. whereas in its property I selected DFDL message domain for input message parsing. Now when I am trying to browse the message it is coming blank.

PS: My XML schema is correct (I have validated it already).