Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-14411

Mappings of source fields named with the character '@' doesn't work in Fuse Online Data Mapper

    XMLWordPrintable

Details

    • % %
    • Todo
    • Hide

      In Fuse Online 7.6 you need to:

      0-Create a new Integration and choosing "API Provider" connector to expose a REST API.

      1- In the API spec should add a data model with a field with "@" character in the name like: "@type" in this json instance example:

      { "id": "some text", "category": "Virtual", "@type": "some text", "orderRelationship": [ { "id": "yup", "@referredType": "ProductTest" }

      ,

      { "id": "12345", "@referredType": "ProductOrder" }

      ]
      }

      2- Use  Data Mapper to map this "@type" field with whatever field in the target of data mapper.

      3-Publish the integration

      4-Make a post request to the deployed service passing "some text" in the @type field.

      5-The result is "null" instead of "some text" as it is expected.

      Show
      In Fuse Online 7.6 you need to: 0-Create a new Integration and choosing "API Provider" connector to expose a REST API. 1- In the API spec should add a data model with a field with "@" character in the name like: "@type" in this json instance example: { "id": "some text", "category": "Virtual", "@type": "some text", "orderRelationship": [ { "id": "yup", "@referredType": "ProductTest" } , { "id": "12345", "@referredType": "ProductOrder" } ] } 2- Use  Data Mapper to map this "@type" field with whatever field in the target of data mapper. 3-Publish the integration 4-Make a post request to the deployed service passing "some text" in the @type field. 5-The result is "null" instead of "some text" as it is expected.

    Description

      This issue can be reproduced in the data mapper component of Fuse Online 7.6.

      Source fields named with the character '@'  apparently can map in the Data Mapper (atlasmap) component but those mappings don't work in runtime .

      Renaming the field without the character '@' works, but unfortunately it isn't feasible because we are implementing this TMF622 Product Ordering API REST Specification R14.5.1, which uses @ to denote attributes that pertain to the model metadata rather than "business"-data. For this reason it is important to support attributes with the character "@" in the field name.

       

      There isn't any error in the pod log. 

       

      Attachments

        1. FuseOnline@issue.png
          162 kB
          Sergio Gutierrez Romero
        2. FuseOnlineIssue2.png
          92 kB
          Sergio Gutierrez Romero

        Activity

          People

            teiid John Verhaeg (Inactive)
            sgutierr@redhat.com Sergio Gutierrez Romero
            Matej Kralik Matej Kralik
            Tomas Plevko
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: