[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1249) Remoting calls do not work with session cookies disabled

[Dan Allen (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1249?page=all ]

Dan Allen updated JBSEAM-1249:
------------------------------

    Attachment: JBSEAM-1249_refactored_with_tests.txt

I want to thank Shane for asking me to create tests because I accomplished two things by doing so:

#1 - The jsUnit tests were not working because the suite was not pointing to the proper location of remoting.js.  All the tests now pass.
#2 - I realized that there were two errors that would have prevented my earlier patches from working.  Worse, they would have caused javascript errors.

The tests that are included confirm that this feature works.  However, I had to pull the extraction of the jsessionid into a helper method so that it was possible to test.  Unfortunately, there is no way to modify window.location.href during tests (and browsers don't have EasyMock).

> Remoting calls do not work with session cookies disabled
> --------------------------------------------------------
>
>                 Key: JBSEAM-1249
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1249
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 1.2.1.GA
>         Environment: Sun Java 5, Linux, Firefox
>            Reporter: Dan Allen
>         Assigned To: Shane Bryzak
>            Priority: Minor
>             Fix For: 1.3.0.BETA1
>
>         Attachments: JBSEAM-1249.txt, JBSEAM-1249_2.txt, JBSEAM-1249_refactored_with_tests.txt, JBSEAM-1249_take3.txt
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Ajax calls in Seam Remoting do not use encoded urls.  Therefore, when session cookies are disabled, the ";jsessionid=" portion of the url is not sent with the request. Therefore, all remoting calls that rely on the HttpSession fail (gracefully).
> A fix would simply augment the Seam.Remoting.sendAjaxRequest to consider the jsessionid if it were present in the initial request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira