[jbossws-issues] [JBoss JIRA] (JBWS-3514) HTTP session scope support

[Alessio Soldano (JIRA)]

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

Alessio Soldano commented on JBWS-3514:
---------------------------------------

Setting dependency on jira for upgrading to CXF to 3.0.2 because of change [1] required.

[1] https://fisheye6.atlassian.com/changelog/cxf?cs=9bc81ab1d1bc5a521fdb0468a9c619289b2dac8e

> HTTP session scope support
> --------------------------
>
>                 Key: JBWS-3514
>                 URL: https://issues.jboss.org/browse/JBWS-3514
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration
>            Reporter: Alessio Soldano
>            Assignee: Jim Ma
>             Fix For: jbossws-cxf-5.0
>
>
> Solerman Kaplon says:
> "Hello everyone, after metro stack got discontinued and CXF becoming the de-facto stack for JbossWS, I'm missing the @HttpSessionScope annotation. Basically, it automatically adds the jsession id to every http response so sessions can be tracked as usual in HTTP. For instance, that allows one to carry CDI/Seam conversations over several WS requests, very useful for rich clients. I would like for something to be included by default in jboss ws to allow for the same level of usability. Right now, the only alternative is to manually fiddle with the webservice context and add the header yourself. Another level of automation would be a Message Handler of Interceptor to do the job. Any other ideas?"
> See also:
> http://weblogs.java.net/blog/kohsuke/archive/2006/10/bringing_state.html



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)