activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <dejan.bosa...@ttmsolutions.com>
Subject Re: Passing in Session ID from client for REST based Messaging
Date Thu, 02 Oct 2008 09:49:45 GMT
The first time you access some web app (REST servlet in this case), the
session will be created by the server and a unique id will be associated
to it. You'll get that info as a jsessionid (usually in a cookie) in a
response to your request. For subsequent calls you have an option to
pass that session id either in a cookie or as a URL parameter, but first
you have to extract it.

That's how session works and there is nothing we can do about it. So I
think it would be easier for clients not supporting cookies to
specifically define a consumer id and avoid using sessions at all.

Cheers

-- 
Dejan Bosanac


http://www.ttmsolutions.com - get a free ActiveMQ user guide

ActiveMQ in Action - http://www.manning.com/snyder/
Scripting in Java - http://www.scriptinginjava.net




OneWhoMikes wrote:
> Thanks for the info.
>
> However, what I'm proposing is not "sessionless" - I just want to be able to
> specify the session id along with the request.
>
> --Mike
>
>
>
> Dejan Bosanac-3 wrote:
>   
>> Hi,
>>
>> you cannot force servlet to create a session with the id you provided. I
>> agree that we have to support sessionless consuming possible. I've
>> created a Jira issue for this
>>
>> https://issues.apache.org/activemq/browse/AMQ-1960
>>
>> Cheers
>>
>> -- 
>> Dejan Bosanac
>>
>>
>> http://www.ttmsolutions.com - get a free ActiveMQ user guide
>>
>> ActiveMQ in Action - http://www.manning.com/snyder/
>> Scripting in Java - http://www.scriptinginjava.net
>>
>>
>> OneWhoMikes wrote:
>>     
>>> I want to configure ActiveMQ to look for a session id in the URL from a
>>> client REST request.  This would allow for the client to pass along it's
>>> own
>>> ID, instead of the server generating one and setting a cookie.
>>>
>>> I found the following posts:
>>> http://www.mojavelinux.com/blog/archives/2006/11/disabling_session_cookies_in_jetty/
>>> http://www.mojavelinux.com/blog/archives/2006/11/disabling_session_cookies_in_jetty/

>>> http://docs.codehaus.org/display/JETTY/SessionIds
>>> http://docs.codehaus.org/display/JETTY/SessionIds 
>>>
>>> Using the above references as a guide, I created the following
>>> jetty-web.xml
>>> file in my webapp's WEB-INF directory:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
>>> "http://jetty.mortbay.org/configure.dtd">
>>> <Configure class="org.mortbay.jetty.webapp.WebAppContext">
>>>     <Get name="sessionHandler">
>>>         <Get name="sessionManager">
>>>             <Set name="usingCookies" type="boolean">false</Set>
>>>         </Get>
>>>     </Get>
>>>
>>>     <Set name="initParams">
>>>         <Map>
>>>             <Entry>
>>>                <Item>org.mortbay.jetty.servlet.SessionURL</Item>
>>>                <Item>xsessionid</Item>
>>>             </Entry>
>>>         </Map>
>>>      </Set>
>>> </Configure>
>>>
>>>
>>> This configuration does disable the cookies, but a new session is being
>>> created for every request - regardless of what I pass in as the
>>> "xsessionid"
>>> parameter with the request.
>>>
>>>
>>> Any help would be greatly appreciated.
>>>
>>>
>>> Thanks,
>>>
>>> Mike
>>>
>>>   
>>>       
>>
>>
>>     
>
>   



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message