Its probably not the servlet - its probably the desktop application. The desktop application needs to send back the session id to the server with each remote method invocation, otherwise the server does not know which session to make available.
Also, if you're using a desktop application sharing session state with a web app, then you'll definitely need to set the session mode = "jsecurity". See the Spring/Webstart application in our Subversion repository for ideas. This will be significantly improved and more 'hands off' for desktop applications when JSecurity 1.0 is released. Cheers, Les On Wed, Feb 4, 2009 at 1:52 PM, jvreeker <[email protected]> wrote: > > I tried that but that is not working, but what I found out is that I have 2 > servlets > CXFServlet using for soap calls for real desktop applications > using org.apache.cxf.transport.servlet.CXFServlet > this is giving message like this > attempting to get session; create = true; session is null = true; session > has id = false > > Dispatcher Servlet is for a webbased application > using org.springframework.web.servlet.DispatcherServlet > > but this one is working. > So It has to do something with the CXFServlet. > hmm... > > Jelle > > -- > View this message in context: > http://n2.nabble.com/using-CXF-with-JSecurity-tp2264471p2270686.html > Sent from the JSecurity User mailing list archive at Nabble.com. > >
