JOPR-216 - jboss-as-5 plugin: Invoking any of the "list*Messages" operations for Topics and Queues that have multiple messages does not produce the correct results

When invoking the "listAllMessages", "listDurableMessages", and "listNonDurableMessages" operations for Topics and Queues that have multiple messages, either an empty table is displayed or a ClassCastException occurs.

Steps to reproduce:

Create a new Queue. Send some messages to the Queue. Invoke the "List All Messages" operation, specifying a selector. The operation fails with the following error:

java.lang.ClassCastException: org.rhq.core.domain.configuration.definition.PropertyDefinitionSimple
at org.rhq.plugins.jbossas5.adapter.api.AbstractPropertyMapAdapter.convertToProperty(AbstractPropertyMapAdapter.java:35)
at org.rhq.plugins.jbossas5.adapter.impl.configuration.AbstractPropertyMapToCompositeValueAdapter.populatePropertyFromMetaValue(AbstractPropertyMapToCompositeValueAdapter.java:99)
at org.rhq.plugins.jbossas5.adapter.impl.configuration.AbstractPropertyMapToCompositeValueAdapter.populatePropertyFromMetaValue(AbstractPropertyMapToCompositeValueAdapter.java:50)
at org.rhq.plugins.jbossas5.adapter.api.AbstractPropertyMapAdapter.convertToProperty(AbstractPropertyMapAdapter.java:40)
at org.rhq.plugins.jbossas5.adapter.api.AbstractPropertyMapAdapter.convertToProperty(AbstractPropertyMapAdapter.java:35)
at org.rhq.plugins.jbossas5.adapter.impl.configuration.PropertyListToCollectionValueAdapter.populatePropertyFromMetaValue(PropertyListToCollectionValueAdapter.java:95)
at org.rhq.plugins.jbossas5.adapter.impl.configuration.PropertyListToCollectionValueAdapter.populatePropertyFromMetaValue(PropertyListToCollectionValueAdapter.java:47)
at org.rhq.plugins.jbossas5.adapter.api.AbstractPropertyListAdapter.convertToProperty(AbstractPropertyListAdapter.java:40)
at org.rhq.plugins.jbossas5.adapter.api.AbstractPropertyListAdapter.convertToProperty(AbstractPropertyListAdapter.java:35)
at org.rhq.plugins.jbossas5.util.ConversionUtils.convertManagedOperationResults(ConversionUtils.java:433)
at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:162)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:511)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

However, invoking the same operation from the JMX Console succeeds and the output is something like:

[JBossMessage[20375444816625664]:PERSISTENT, JBossMessage[20375444816805889]:PERSISTENT]