Uploaded image for project: 'Blacktie'
  1. Blacktie
  2. BLACKTIE-327

Support transcoding of message payload to XML

    Details

      Description

      Currently the message payload is placed onto the wire directly (atmibroker-hyrbid/BufferConverterImpl.cxx) although it is padded to ensure that different machine architectures can read the data successfully.

      It is proposed to add an option to encode the data on the wire in XML which should prove useful for routing the request.

      The XML format should support all our buffer types:
      X_OCTET
      X_COMMON
      X_C_TYPE
      BT_PBF

      char[] data should be encoded into the XML buffer as base64 data

      An example buffer would look like:

      <myXsd:FLIGHT_RESULT>
      <myXsd:FLIGHT_NO>a7vROi2</myXsd:FLIGHT_NO>
      <myXsd:DEPART_CITY>a7vROi2</myXsd:DEPART_CITY>
      <myXsd:ARRIVE_CITY>a7vROi2</myXsd:ARRIVE_CITY>
      <myXsd:DATE>a7vROi2</myXsd:DATE>
      </myXsd:FLIGHT_RESULT>

      See https://jira.jboss.org/browse/BLACKTIE-328 to see how the schema looks like.

      It is envisaged that this would affect both Java and C++
      It will affect configuration
      It will affect atmibroker-hybrid
      It should not affect atmibroker-xatmi or the java equivalent as the encoding should be transparent to the user.

      Note we should try to ensure that what we do here is compatible with: https://jira.jboss.org/browse/BLACKTIE-202

      It would be interesting to investigate whether it is possible to encode the message in SOAP rather than raw XML to help with: https://jira.jboss.org/browse/BLACKTIE-329

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  zhfeng Amos Feng
                  Reporter:
                  tomjenkinson Tom Jenkinson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 3 weeks
                    3w
                    Remaining:
                    Remaining Estimate - 3 weeks
                    3w
                    Logged:
                    Time Spent - Not Specified
                    Not Specified