On Sat, Mar 24, 2012 at 1:32 AM, karthi <rathinasamy....@snovabits.net> wrote:
> Hi,
>
> I am developing an application using tapestry (my first app), in that am
> using cookies like below
>
> public class Portfolio {
>
> @org.apache.tapestry5.ioc.annotations.Inject
> private Cookies cookies;
>
> cookies.writeCookieValue("isUserLogin", "True", 60*60);
> cookies.writeCookieValue("userId", userId, 60*60);
>
> and read from cookie value by this method
>
> cookies.readCookieValue("userIdent");
>
> I have tested this in firefox browser, Iphone OS 4, Android HTC, Android
> Samsung galaxy s2 and in some other phones this cookie is working great in
> all these phones, I can able to see my sysouts logs regarding cookeis etc.,
>
> But in samsung galaxy nexus s (Android OS version 2.3.6) this cookies not
> get write or saved...?
>
> For testing purpose we wrote a single file to save this cookies, in that
> also it dint write, however if I used javax.servlet.http.Cookie; the value
> get writes in the phone!
>
> What should have caused this problem?
> Am I miss anything in code?
> Can anyone help me to find the root cause here?
>
> }
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry5-services-cookies-not-get-writes-in-samsung-galaxy-nexus-s-tp5591264p5591264.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
I guess your're really doing:
cookies.readCookieValue("userId");
(You corrected your Nabble post, but mailing list users don't see such updates.)
The Tapestry 5 Cookies API
(http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/Cookies.html)
is only a very simple façade in front of javax.servlet.http.Cookie,
and is missing some basic functionality (can't specify the secure flag
per TAP5-47, can't set a cookie having a domain+path+max-age
combination per TAP5-1394/TAP5-1858, no ability to delete a session
cookie having a domain).
Can you provide the exact method in javax.servlet.http.Cookie (and its
parameters) that works for you? I'm guessing it's a variation that
doesn't have an exact match in the Tapestry Cookies API. In that case,
you might have to use the javax.servlet.http.Cookie class directly or
maybe provide a custom implementation of
org.apache.tapestry5.services.Cookies
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
