Session id missing

>
> On Thu, 8 Sep 2005 21:15:28 +0100, "Boon Low" <[hidden email]>  
> said:
>
>> Hi,
>>
>> I am attempting to obtain the session id using the request generator
>> processor. But the returned request tree doesn't include the session
>> id <requested-session-id/> element. I have tested this using the
>> following simple page flow and xpl and invoked the path a browser:
>> ..
>>
>
> Do you have cookies disabled in the browser?  I had the same thing
> initially, until I remembered to enable them.
>
> Once I enabled them and hit refresh a couple of times the session id
> showed up.
>
> -- Regards, Dan S
>
>
> --
> http://www.fastmail.fm - Email service worth paying for. Try it for  
> free
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws
>

> Hi,
>
> I have cookies enabled so this shouldn't be the issue. I rerun the  
> app later and checked that the ID mysteriously appeared.
>
> Delving deeper into this, I discovered this is because I have  
> referred to the root server directory. If I points to the the server  
> root (examples - http://localhost:8080/ops/), the container writes  
> the session id. But if I go to the direct examples, e.g. http://
> localhost:8080/ops/xforms-controls (without first going to the root),  
> the contains didn't generate the session ID. And I am building the  
> app which needed to be invoked as http://localhost:8080/ops/myapp   
> first and foremost.
>
> Any idea of this bizarre behavior? I noticed the root ops  
> installation uses portlet instead of servlet. Something in the  
> epilogue needs to be modified?

>
> On Tue, 13 Sep 2005 10:32:14 +0100, "Boon Low" <[hidden email]>  
> said:
>
>
>> Hi,
>>
>> I have cookies enabled so this shouldn't be the issue. I rerun the
>> app later and checked that the ID mysteriously appeared.
>>
>> Delving deeper into this, I discovered this is because I have
>> referred to the root server directory. If I points to the the server
>> root (examples - http://localhost:8080/ops/), the container writes
>> the session id. But if I go to the direct examples, e.g. http://
>> localhost:8080/ops/xforms-controls (without first going to the root),
>> the contains didn't generate the session ID. And I am building the
>> app which needed to be invoked as http://localhost:8080/ops/myapp
>> first and foremost.
>>
>> Any idea of this bizarre behavior? I noticed the root ops
>> installation uses portlet instead of servlet. Something in the
>> epilogue needs to be modified?
>>
>>
>
> Don't think so.  I think it is the case that session ids are generated
> unless they are needed.  So if for example you use authentication  
> or the
> scope serializer then a session id will be generated.
>
> I dumped the code you sent into the project created by New | Project
> in the Studio plugin and found no session id present.  Then I changed
> your pipeline to be
>
> <p:config
>     xmlns:p="http://www.orbeon.com/oxf/pipeline"
>    xmlns:oxf="http://www.orbeon.com/oxf/processors"
>
>
>>
>>
>>
> <p:param name="instance" type="input"/>
> <p:param name="data" type="output"/>
> <p:processor name="oxf:request"
> xmlns:p="http://www.orbeon.com/oxf/pipeline">
>   <p:input name="config">
>     <config>
>       <include>/</include>
>     </config>
>   </p:input>
>   <p:output name="data" ref="data"/>
> </p:processor>
> <p:processor name='oxf:scope-serializer' >
>     <p:input name="config" >
>      <config>
>        <key>cart</key>
>        <scope>session</scope>
>       </config>
>     </p:input>
>     <p:input name="data" >
>         <blah/>
>     </p:input>
>  </p:processor>
> </p:config>
>
> .  With this I saw the following :
> 1.  When I first when to myapp/showRequest what was displayed
>     in the browser was the request document with no session id
>     present.
> 2.  However if I looked at what cookies were present, I found
>     that I had a new cookie as a result of the request.
> 3.  If I reloaded the page the session id would be visible
>     the request document.
>
> Hope this helps.
>
> -- Regards, Dan S
>
> --
> http://www.fastmail.fm - Send your email first class
>
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws
>
>

> Dan,
>
> Thank you for this lead, it's would useful to include a page prior to  
> the request to generate the ID. I've started to experiment with the  
> scope processors, using them to generate unique ID within the app  
> (uuid) and put them into session scope.
>
> Btw, I need the ID to convert XML into base64 binary by serializing  
> XML data into file (per unique session) and read them back as binary  
> (required for sending to a web service). Can't see there is a more  
> straight-forward way to do so?

>
>
> Boon
>
>
> On 13 Sep 2005, at 12:03, [hidden email] wrote:
>
>
> >
> > On Tue, 13 Sep 2005 10:32:14 +0100, "Boon Low" <[hidden email]>  
> > said:
> >
> >
> >> Hi,
> >>
> >> I have cookies enabled so this shouldn't be the issue. I rerun the
> >> app later and checked that the ID mysteriously appeared.
> >>
> >> Delving deeper into this, I discovered this is because I have
> >> referred to the root server directory. If I points to the the server
> >> root (examples - http://localhost:8080/ops/), the container writes
> >> the session id. But if I go to the direct examples, e.g. http://
> >> localhost:8080/ops/xforms-controls (without first going to the root),
> >> the contains didn't generate the session ID. And I am building the
> >> app which needed to be invoked as http://localhost:8080/ops/myapp
> >> first and foremost.
> >>
> >> Any idea of this bizarre behavior? I noticed the root ops
> >> installation uses portlet instead of servlet. Something in the
> >> epilogue needs to be modified?
> >>
> >>
> >
> > Don't think so.  I think it is the case that session ids are generated
> > unless they are needed.  So if for example you use authentication  
> > or the
> > scope serializer then a session id will be generated.
> >
> > I dumped the code you sent into the project created by New | Project
> > in the Studio plugin and found no session id present.  Then I changed
> > your pipeline to be
> >
> > <p:config
> >     xmlns:p="http://www.orbeon.com/oxf/pipeline"
> >    xmlns:oxf="http://www.orbeon.com/oxf/processors"
> >
> >
> >>
> >>
> >>
> > <p:param name="instance" type="input"/>
> > <p:param name="data" type="output"/>
> > <p:processor name="oxf:request"
> > xmlns:p="http://www.orbeon.com/oxf/pipeline">
> >   <p:input name="config">
> >     <config>
> >       <include>/</include>
> >     </config>
> >   </p:input>
> >   <p:output name="data" ref="data"/>
> > </p:processor>
> > <p:processor name='oxf:scope-serializer' >
> >     <p:input name="config" >
> >      <config>
> >        <key>cart</key>
> >        <scope>session</scope>
> >       </config>
> >     </p:input>
> >     <p:input name="data" >
> >         <blah/>
> >     </p:input>
> >  </p:processor>
> > </p:config>
> >
> > .  With this I saw the following :
> > 1.  When I first when to myapp/showRequest what was displayed
> >     in the browser was the request document with no session id
> >     present.
> > 2.  However if I looked at what cookies were present, I found
> >     that I had a new cookie as a result of the request.
> > 3.  If I reloaded the page the session id would be visible
> >     the request document.
> >
> > Hope this helps.
> >
> > -- Regards, Dan S
> >
> > --
> > http://www.fastmail.fm - Send your email first class
> >
> >
> >
> > --
> > You receive this message as a subscriber of the ops-
> > [hidden email] mailing list.
> > To unsubscribe: mailto:[hidden email]
> > For general help: mailto:[hidden email]?subject=help
> > ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> > wws
> >
> >
>
>
>