[
https://jira.jboss.org/jira/browse/JBAS-7024?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBAS-7024.
---------------------------------
Resolution: Done
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.
results of list*Messages methods of Queues and Topics have wrong meta
type definition
-------------------------------------------------------------------------------------
Key: JBAS-7024
URL:
https://jira.jboss.org/jira/browse/JBAS-7024
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: JBAPP_5_0 rev90256
Reporter: Lukas Krejci
Assignee: Scott M Stark
Priority: Critical
Attachments: JBAS-7024.patch
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira