Support jms 1.0.2 for SeeBeyond SRE504

[arinban]

There is a need to be able to utilise the generic RA with the Sun Application Server 8.1 and jre 1.4.2_08 to integrate with SeeBeyond SRE504. We have discovered that this version of SeeBeyond utilises the jms spec version 1.0.2 and I understand generic RA and J2EE 1.4 supports 1.1.

We therefore have an urgent need to get Generic RA to support this earlier version of the jms spec.

Environment

Operating System: All Platform: All

Affected Versions

[current]

[arinban]

• Issue Imported From: https://github.com/ari-ban/test1/issues/11
• 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/11
• 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/11
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@glassfishrobot

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Reported by markmundy

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: Inbound code has dependency on unified connection factory of jms 1.1. For old jms versions, that will be a problem.

It need to be enhanced to take care of jms 1.0.2.

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: The inbound code has been enhanced to support JMS 1.0.2. We have posted 1.5 RC1, which contain this fix.

Following new properties are added.

1. UnifiedDestinationClassName (for RA, AdminObject and MCF, applicable only for javabean mode) 2. DeadMessageDestinationType (For MDB ActivationSpec, applicable for both javabean and jndi modes of integration) 3. DeadMessageDestinationJndiName (for MDB Activation type. Applicable for only jndi mode) 4. DeadMessageConnectionFactoryJndiName(for MDB Activation type. Applicable for only jndi mode) 5. DeadMessageConnectionFactoryProperties(for MDB Activation type. Applicable for only javabean mode)

All these information will be updated in userguide shortly.

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: The inbound code has been enhanced to support JMS 1.0.2. Generic JMS RA 1.5 RC1 that contain the changes has been posted in the "Documents and Files" section.

Following new properties are added.

1. UnifiedDestinationClassName (for RA, AdminObject and MCF, applicable only for javabean mode) 2. DeadMessageDestinationType (For MDB ActivationSpec, applicable for both javabean and jndi modes of integration) 3. DeadMessageDestinationJndiName (for MDB Activation type. Applicable for only jndi mode) 4. DeadMessageConnectionFactoryJndiName(for MDB Activation type. Applicable for only jndi mode) 5. DeadMessageConnectionFactoryProperties(for MDB Activation type. Applicable for only javabean mode)

All these information will be updated in userguide shortly.

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented @sivakumart said: Added fix keyword

[arinban]

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

[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-11

[arinban]

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