[seam-issues] [JBoss JIRA] (JBSEAM-5060) SOAPRequestHandler does not perform standard context cleanup

Martin Kouba (JIRA) jira-events at lists.jboss.org
Thu Nov 22 06:53:21 EST 2012

    [ https://issues.jboss.org/browse/JBSEAM-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736345#comment-12736345 ] 

Martin Kouba commented on JBSEAM-5060:

In fact {{SOAPRequestHandler}} does perform some cleanup, it calls {{Lifecycle.endRequest()}} prior to dispatching a message - see also {{SOAPRequestHandler.close(MessageContext)}}. The question is why {{ServletLifecycle.endRequest()}} is not used instead. It seems the only difference between these methods is HTTP session handling.
> SOAPRequestHandler does not perform standard context cleanup
> ------------------------------------------------------------
>                 Key: JBSEAM-5060
>                 URL: https://issues.jboss.org/browse/JBSEAM-5060
>             Project: Seam 2
>          Issue Type: Bug
>          Components: WS
>    Affects Versions: 2.2.2.Final, 2.3.0.Final
>            Reporter: Martin Kouba
>            Assignee: Marek Novotny
>            Priority: Minor
> {{SOAPRequestHandler}} only calls {{ServletLifecycle.beginRequest()}} for inbound message, but no {{ServletLifecycle.endRequest()}} for outbound message. This might be intentional, but also a bug.
> One of the consequences is that it's not possible to implement stateless web service or logout operation ({{org.jboss.seam.web.Session.invalidate()}} doesn't work).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the seam-issues mailing list