Lingo

Add support for JMS 1.0.2

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0
  • Fix Version/s: 1.4
  • Labels:
    None
  • Number of attachments :
    2

Description

Lingo does not support JMS 1.0.2; or at least, the DefaultJmsProducer doesn't.

DefaultJmsProducer.newInstance(ConnectionFactory) will only work with a 1.1 version ConnectionFactory .

Maybe there should be a DefaultJms102Producer as well?

  1. Java Source File
    JmsProducerConfig102.java
    27/Feb/08 2:17 AM
    3 kB
    Radek Porazil
  2. Java Source File
    MultiplexingRequestor102.java
    27/Feb/08 2:17 AM
    4 kB
    Radek Porazil

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
james strachan added a comment -

fancy submitting your patch?

Show
james strachan added a comment - fancy submitting your patch?
Hide
Permalink
Radek Porazil added a comment -

I had to use JMS 1.0.2 for one of my projects on WLS8.1 and I somehow solved the issue (it is not particularly well documented and it even might not be complete as my application uses Lingo just as infrastructure).
However, I believe, that attached files might be good start for people facing the same problem. Add the attached files to your project, do some refactoring if you need to and of course modify your Spring application context :

<bean id="producerConfig" class="org.lingo102.JmsProducerConfig102"/>

<bean id="jmsRequestor" class="org.lingo102.MultiplexingRequestor102" factory-method="newInstance">
<constructor-arg ref="jmsFactory"/>
<constructor-arg ref="requestDestination"/>
</bean>

Show
Radek Porazil added a comment - I had to use JMS 1.0.2 for one of my projects on WLS8.1 and I somehow solved the issue (it is not particularly well documented and it even might not be complete as my application uses Lingo just as infrastructure). However, I believe, that attached files might be good start for people facing the same problem. Add the attached files to your project, do some refactoring if you need to and of course modify your Spring application context : <bean id="producerConfig" class="org.lingo102.JmsProducerConfig102"/> <bean id="jmsRequestor" class="org.lingo102.MultiplexingRequestor102" factory-method="newInstance"> <constructor-arg ref="jmsFactory"/> <constructor-arg ref="requestDestination"/> </bean>

People

  • Assignee:
    Unassigned
    Reporter:
    James Webster
Vote (4)
Watch (6)

Dates

  • Created:
    Updated: