[ https://issues.jboss.org/browse/GTNWSRP-282?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-282: ------------------------------------------------- Jared MORGAN <jmorgan(a)redhat.com&gt; made a comment on [bug 803544|https://bugzilla.redhat.com/show_bug.cgi?id=803544] Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -Cause: The cookie session handler and the ws-security handler were not being set in the right order. +The cookie session handler was not being set on each request from the producer and the consumer when ws-security was enabled. A session was created on each request, and any portlets that relied on sessions would not function properly. The fix implements changes to the order of the web service handlers that ensure the session is properly added on each invocation between the consumer and producer. Sessions now work properly with WSRP when WS-Security is enabled- -Consequence: The session was not being set on each request from the producer and the consumer when ws-security was enabled. This meant that on each request a session was being created and any portlets which relied on sessions would not function properly. - -Fix: Change the order of the web service handlers so that the session would be properly added on each invocation between the consumer and producer. - -Result: Sessions now work properly with WSRP when WS-Security is enabled -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira