How to access STOMP getSessionAttributes() that are populated in websocket client-inbound-channel interceptor...











up vote
1
down vote

favorite












I am using spring-websocket and I have these two interceptors



<websocket:client-inbound-channel>
<websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
<websocket:interceptors>
<ref bean="myInterceptor"/>
</websocket:interceptors>
</websocket:client-inbound-channel>


<websocket:client-outbound-channel>
<websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
<websocket:interceptors>
<ref bean="myOutInterceptor"/>
</websocket:interceptors>
</websocket:client-outbound-channel>


I am using StompHeaderAccessor to wrap the message in preSend(Message<?> message, MessageChannel channel) in both interceptors.



I am using the following to access session's attributes in the inbound interceptor:



...
StompHeaderAccessor sha = StompHeaderAccessor.wrap(message);
// ignore non-STOMP messages like heartbeat messages
if(sha.getCommand() == null) {
return message;
}
String sessionId = sha.getSessionId();
Map<String, Object> sessionAttributes = sha.getSessionAttributes();
...


The problem is, sha.getSessionAttributes(); in the inbound interceptor returns data but when I call sha.getSessionAttributes(); in the outbound interceptor it returns null.



How can I access the sessionAttributes from the outbound Interceptor?










share|improve this question




























    up vote
    1
    down vote

    favorite












    I am using spring-websocket and I have these two interceptors



    <websocket:client-inbound-channel>
    <websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
    <websocket:interceptors>
    <ref bean="myInterceptor"/>
    </websocket:interceptors>
    </websocket:client-inbound-channel>


    <websocket:client-outbound-channel>
    <websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
    <websocket:interceptors>
    <ref bean="myOutInterceptor"/>
    </websocket:interceptors>
    </websocket:client-outbound-channel>


    I am using StompHeaderAccessor to wrap the message in preSend(Message<?> message, MessageChannel channel) in both interceptors.



    I am using the following to access session's attributes in the inbound interceptor:



    ...
    StompHeaderAccessor sha = StompHeaderAccessor.wrap(message);
    // ignore non-STOMP messages like heartbeat messages
    if(sha.getCommand() == null) {
    return message;
    }
    String sessionId = sha.getSessionId();
    Map<String, Object> sessionAttributes = sha.getSessionAttributes();
    ...


    The problem is, sha.getSessionAttributes(); in the inbound interceptor returns data but when I call sha.getSessionAttributes(); in the outbound interceptor it returns null.



    How can I access the sessionAttributes from the outbound Interceptor?










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I am using spring-websocket and I have these two interceptors



      <websocket:client-inbound-channel>
      <websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
      <websocket:interceptors>
      <ref bean="myInterceptor"/>
      </websocket:interceptors>
      </websocket:client-inbound-channel>


      <websocket:client-outbound-channel>
      <websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
      <websocket:interceptors>
      <ref bean="myOutInterceptor"/>
      </websocket:interceptors>
      </websocket:client-outbound-channel>


      I am using StompHeaderAccessor to wrap the message in preSend(Message<?> message, MessageChannel channel) in both interceptors.



      I am using the following to access session's attributes in the inbound interceptor:



      ...
      StompHeaderAccessor sha = StompHeaderAccessor.wrap(message);
      // ignore non-STOMP messages like heartbeat messages
      if(sha.getCommand() == null) {
      return message;
      }
      String sessionId = sha.getSessionId();
      Map<String, Object> sessionAttributes = sha.getSessionAttributes();
      ...


      The problem is, sha.getSessionAttributes(); in the inbound interceptor returns data but when I call sha.getSessionAttributes(); in the outbound interceptor it returns null.



      How can I access the sessionAttributes from the outbound Interceptor?










      share|improve this question















      I am using spring-websocket and I have these two interceptors



      <websocket:client-inbound-channel>
      <websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
      <websocket:interceptors>
      <ref bean="myInterceptor"/>
      </websocket:interceptors>
      </websocket:client-inbound-channel>


      <websocket:client-outbound-channel>
      <websocket:executor core-pool-size="100" max-pool-size="200" keep-alive-seconds="600"/>
      <websocket:interceptors>
      <ref bean="myOutInterceptor"/>
      </websocket:interceptors>
      </websocket:client-outbound-channel>


      I am using StompHeaderAccessor to wrap the message in preSend(Message<?> message, MessageChannel channel) in both interceptors.



      I am using the following to access session's attributes in the inbound interceptor:



      ...
      StompHeaderAccessor sha = StompHeaderAccessor.wrap(message);
      // ignore non-STOMP messages like heartbeat messages
      if(sha.getCommand() == null) {
      return message;
      }
      String sessionId = sha.getSessionId();
      Map<String, Object> sessionAttributes = sha.getSessionAttributes();
      ...


      The problem is, sha.getSessionAttributes(); in the inbound interceptor returns data but when I call sha.getSessionAttributes(); in the outbound interceptor it returns null.



      How can I access the sessionAttributes from the outbound Interceptor?







      java spring-websocket






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 20 at 8:22









      Ashish Kamble

      621419




      621419










      asked Nov 20 at 8:19









      aboudirawas

      218




      218
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          It feels like a workaround. That is how I solved it.



          I added a bean acting like a repository containing a Map, keys are session ids, values are session attributes.



          In inbound interceptor, case SUBSCRIBE, I put the session id along with the attributes. And removed it from the map in case UNSUBSCRIBE and case DISCONNECT.



          In outbound interceptor, case MESSAGE, I got the relevant sessionAttributes from that bean sessionAttributes = theBean.getSessionIdAndAttributes().get(sessionId) instead of getting it from the message object sessionAttributes = sha.getSessionAttributes().






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53388803%2fhow-to-access-stomp-getsessionattributes-that-are-populated-in-websocket-clien%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote



            accepted










            It feels like a workaround. That is how I solved it.



            I added a bean acting like a repository containing a Map, keys are session ids, values are session attributes.



            In inbound interceptor, case SUBSCRIBE, I put the session id along with the attributes. And removed it from the map in case UNSUBSCRIBE and case DISCONNECT.



            In outbound interceptor, case MESSAGE, I got the relevant sessionAttributes from that bean sessionAttributes = theBean.getSessionIdAndAttributes().get(sessionId) instead of getting it from the message object sessionAttributes = sha.getSessionAttributes().






            share|improve this answer

























              up vote
              0
              down vote



              accepted










              It feels like a workaround. That is how I solved it.



              I added a bean acting like a repository containing a Map, keys are session ids, values are session attributes.



              In inbound interceptor, case SUBSCRIBE, I put the session id along with the attributes. And removed it from the map in case UNSUBSCRIBE and case DISCONNECT.



              In outbound interceptor, case MESSAGE, I got the relevant sessionAttributes from that bean sessionAttributes = theBean.getSessionIdAndAttributes().get(sessionId) instead of getting it from the message object sessionAttributes = sha.getSessionAttributes().






              share|improve this answer























                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                It feels like a workaround. That is how I solved it.



                I added a bean acting like a repository containing a Map, keys are session ids, values are session attributes.



                In inbound interceptor, case SUBSCRIBE, I put the session id along with the attributes. And removed it from the map in case UNSUBSCRIBE and case DISCONNECT.



                In outbound interceptor, case MESSAGE, I got the relevant sessionAttributes from that bean sessionAttributes = theBean.getSessionIdAndAttributes().get(sessionId) instead of getting it from the message object sessionAttributes = sha.getSessionAttributes().






                share|improve this answer












                It feels like a workaround. That is how I solved it.



                I added a bean acting like a repository containing a Map, keys are session ids, values are session attributes.



                In inbound interceptor, case SUBSCRIBE, I put the session id along with the attributes. And removed it from the map in case UNSUBSCRIBE and case DISCONNECT.



                In outbound interceptor, case MESSAGE, I got the relevant sessionAttributes from that bean sessionAttributes = theBean.getSessionIdAndAttributes().get(sessionId) instead of getting it from the message object sessionAttributes = sha.getSessionAttributes().







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 at 9:14









                aboudirawas

                218




                218






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53388803%2fhow-to-access-stomp-getsessionattributes-that-are-populated-in-websocket-clien%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Feedback on college project

                    Futebolista

                    Albești (Vaslui)