Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-7024

results of list*Messages methods of Queues and Topics have wrong meta type definition

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Critical Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.M1
    • Component/s: None
    • Security Level: Public (Everyone can see)
    • Environment:
      JBAPP_5_0 rev90256
    • Similar Issues:
      Show 10 results 

      Description

      The MessageListMapper used to define the meta types on list*Messages() methods for Queues and Topics advertises that the resulting type will be:

      CollectionMetaType[ImmutableCompositeMetaType["JMSMessageID" = SimpleMetaType.STRING, "JMSCorrelationID" = SimpleMetaType.STRING, "JMSTimestamp" = SimpleMetaType.LONG]]

      however the meta type of the actual meta values obtained using collectionValue.getElements() is advertised as:

      MapCompositeValue[ImmutableCompositeMetaType["JMSMessageID" = SimpleMetaType.STRING, "JMSCorrelationID" = SimpleMetaType.STRING, "JMSTimestamp" = SimpleMetaType.LONG]]

      This discrepancy is affecting the admin console, Jopr and JON because the meta values values have different type than the advertised meta type.

        Issue Links

          Activity

          Hide
          Lukas Krejci
          added a comment -

          I'm attaching a simple patch that fixed the issue for me.

          Show
          Lukas Krejci
          added a comment - I'm attaching a simple patch that fixed the issue for me.
          Hide
          Scott Stark
          added a comment -

          I have applied the patch to produce a CompositeValueSupport, but the existing
          MapCompositeValue is a CompositeValue and should be seen as consistent with the declared CompositeMetaType.

          Show
          Scott Stark
          added a comment - I have applied the patch to produce a CompositeValueSupport, but the existing MapCompositeValue is a CompositeValue and should be seen as consistent with the declared CompositeMetaType.

            People

            • Assignee:
              Scott Stark
              Reporter:
              Lukas Krejci
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: