Hi Scott, How should I be accessing the URL for my app? Would I be by-passing the portal url entirely and accessing the web app url for my portlet app? Or is there a special portal URL that dispatches to my app and carries the portal sesion with it? I guess I may be stumbling on something even more basic...
Thanks, Chris On 6/30/05, Scott T Weaver <[EMAIL PROTECTED]> wrote: > > Hmmmm, I think we need to append the JSESSION_ID to the url since I doubt > the Ajax requests carry any cookies with them. > > -Scott > > > -----Original Message----- > > From: Chris Custine [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 29, 2005 8:09 PM > > To: Jetspeed Users Mailing List > > Subject: J2 - Ajax from portlet / need request.getUserPrincipal, etc. > > > > OK, I am having a quick go at doing some Ajax interactions from browser > to > > my portlet app. Everything looks good so far as long as I don't need > > access > > to session data (which will almost always be necessary). In my normal > > portlet usage I use request.getUserPrincipal() for userid and I will > also > > need access to session info. When I map the calls directly to the web > app > > via its URL it creates a new session and the userprincipal is null. Has > > anyone else experimented with something like this yet and can offer any > > pointers? > > > > Thanks, > > Chris > >
