Results 1 to 2 of 2

Thread: problem I can't figure out with spring jms remoting

  1. #1
    Join Date
    Nov 2007
    Location
    DalianCity, Liaoning Province, China
    Posts
    11

    Talking problem I can't figure out with spring jms remoting

    hi, guys

    I find a problem with spring jms remoting, maybe it's not problem, here is the details:

    when I use DefaultMessageListenerContainer with JmsInvokerServiceExporter, the Message can't be received and can't be processed either,
    but when I change the container type to SimpleMessageListenerContainer, it works, this behavior confused me.

    as to the javadoc of JmsInvokerServiceExporter, it deemed to be used with DefaultMessageListenerContainer :
    * <p>Note that this class implements Spring's
    * {@link org.springframework.jms.listener.SessionAwareMessa geListener}
    * interface, since it requires access to the active JMS Session.
    * Hence, this class can only be used with message listener containers
    * which support the SessionAwareMessageListener interface (e.g. Spring's
    * {@link org.springframework.jms.listener.DefaultMessageLis tenerContainer}).
    but why DefaultMessageListenerContainer doesn't work , and SimpleMessageListenerContainer do?!

    who can help me find out the truth behind this?!
    Dalian City, China

  2. #2
    Join Date
    Nov 2007
    Location
    DalianCity, Liaoning Province, China
    Posts
    11

    Default

    aaaaaaa, sorry,
    maybe it's a problem with <jms:listener>

    when I use the traditional bean defintion, simple and default message listener container both work,

    Dalian City, China

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •