Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-375

Add callback functionality to transport connections

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.6
    • Component/s: Core
    • Labels:
      None

      Description

      We are using the WebserviceMessageListener and I would like to log the header attributes (like correlationId and replyTo) of the incomming and outgoing JMS messages.

      I can log the header values of incomming messages by extending the WebserviceMessageListener but the response messages are created within the spring ws framework.

      It would be nice if you can manipulate, or log the JMS Message before it is send by the message producer.

      Possible solution: Add callback functionality to the JmsReceiverConnection

        Activity

        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Fixed. JMS transport now allows for a org.springframework.jms.core.MessagePostProcessor to be injected, which can be used to change the message.

        Show
        arjen.poutsma Arjen Poutsma added a comment - Fixed. JMS transport now allows for a org.springframework.jms.core.MessagePostProcessor to be injected, which can be used to change the message.
        Hide
        jethrobakker Jethro Bakker added a comment -

        It is now possible to change/log the outgoing message but I think it is still not possible to log incomming messages with its attributes. Is this a correct conclusion?

        Show
        jethrobakker Jethro Bakker added a comment - It is now possible to change/log the outgoing message but I think it is still not possible to log incomming messages with its attributes. Is this a correct conclusion?
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Yes, that is correct.

        Show
        arjen.poutsma Arjen Poutsma added a comment - Yes, that is correct.
        Hide
        jethrobakker Jethro Bakker added a comment -

        Ok.

        We want to do the following: If an expiration time is set on the request message than we have to set also an expiration time on the response message. The value of the expiration time is calculated as follows: time of request expiration minus current time.

        We want such a solution because the request sender determines the time the sending system is waiting on the response message. When this system times out the response message must directly expire on the queue.

        But with the current solution this is not possible, because you can not correlate request and response message.

        Show
        jethrobakker Jethro Bakker added a comment - Ok. We want to do the following: If an expiration time is set on the request message than we have to set also an expiration time on the response message. The value of the expiration time is calculated as follows: time of request expiration minus current time. We want such a solution because the request sender determines the time the sending system is waiting on the response message. When this system times out the response message must directly expire on the queue. But with the current solution this is not possible, because you can not correlate request and response message.
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Closing old issues

        Show
        arjen.poutsma Arjen Poutsma added a comment - Closing old issues

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            jethrobakker Jethro Bakker
          • Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: