WAS-ActiveMQ integration: JMS provider throws class cast exception

[arinban]

Some JMS providers throw class cast exception if the destination object is not exectly the one implemented by the provider.

e-mail from an engineer working on WAS - ActiveMQ integration using genericjmsra

In digging a bit deeper, I notice that genericjmsra adapter does not proxy all the jms classes(specifically in this case, the javax.jms.Message and its variants). Also, I notice that the ActiveMQMessage class expects the destination to be passed in to be an ActiveMQDestination(therefore it can't be any other jms provider's destination and specifically it can't be the Adapter's QueueProxy class). Anyway, I'm trying to figure out what's the expectation here. Should the ActiveMQMessage class be expected to deal with any ole destination out there? Or is the exepectation that the genericjmsra needs to be fixed so that it proxies additional jms classes so that it can intercept and do the right thing when methods such as setJMSReplyTo is invoked?

Environment

Operating System: All Platform: All

Affected Versions

[0.9]

[arinban]

• Issue Imported From: https://github.com/ari-ban/test1/issues/15
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@arinban

[arinban]

@arinban Commented

• Issue Imported From: https://github.com/ari-ban/glassfish-genericjmsra/issues/15
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@arinban

[arinban]

@arinban Commented @arinban Commented

• Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/15
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@glassfishrobot

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Reported by binod

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: A new property called UseProxyMessages has been introduced. If you set this property, resource adapter will create a proxy class for implementing javax.jms.Message. In the proxy handler, the destination object is unwrapped for setJMSReplyTo and setJMSDestination objects.

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: Adding keyword

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: Fixed wrong keyword

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented @sivakumart said: fixed in milestone 1.6

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Was assigned to binod

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-15

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Marked as fixed on Sunday, September 5th 2010, 8:21:08 pm