Closed arinban closed 6 years ago
Original Issue:https://github.com/javaee/glassfish-genericjmsra/issues/11 Raised By:@glassfishrobot Created at:Fri Dec 23 07:07:05 IST 2005 Assigned To:@glassfishrobot
@glassfishrobot Commented on Fri Dec 23 07:07:05 IST 2005 Reported by markmundy
@glassfishrobot Commented on Fri Dec 23 07:20:09 IST 2005 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.
@glassfishrobot Commented on Fri Dec 30 03:53:40 IST 2005 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.
@glassfishrobot Commented on Fri Dec 30 03:56:15 IST 2005 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.
@glassfishrobot Commented on Wed Mar 15 05:45:21 IST 2006 @sivakumart said: Added fix keyword
@glassfishrobot Commented on Wed Mar 15 05:47:23 IST 2006 @sivakumart said: fixed in milestone 1.5
@glassfishrobot Commented on Fri Dec 23 07:07:05 IST 2005 Was assigned to binod
@glassfishrobot Commented on Mon Apr 24 13:01:27 IST 2017 This issue was imported from java.net JIRA GENERICJMSRA-11
@glassfishrobot Commented on Mon Sep 06 08:51:08 IST 2010 Marked as fixed on Sunday, September 5th 2010, 8:21:08 pm
@glassfishrobot Closed the issue on Mon Sep 06 08:51:08 IST 2010
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]