02-10-2010 03:14 AM
Hi,
I am developing application for Strom.
I my application consumes webservices. I am using the same object everytime to maintain the session.
And the application is running fine on Storm1.
But when i run my application on storm2, then i receive the error session expired.
Does anybody has some idea whats the issue with storm2.
Thanks,
Rahul
02-10-2010 03:36 AM
pretty sure it is not an error of the phone. try to debug your code. do you use static variables somewhere?
without additional info it is hard to help.
02-10-2010 04:05 AM
Ya, i am using static variables.
But my webservice object remains the same everytime i call any webservice function.
02-10-2010 05:31 AM
I am using wifi connection in case of storm2 and using GPRS connection in storm1 ( because wifi connection is not available in storm1). Does it has to do something with session problem?
02-10-2010 05:44 AM
crystal ball is all fuzzy. you'll have to provide some code or do more research on your own.
02-10-2010 05:53 AM
Shall i provide you my stub generated class?
I have also tried setting up, SESSION_MAINTAIN_PROPERTY property in stub class. But that didnt worked.
02-11-2010 04:33 AM
02-11-2010 04:41 AM
session management is dependent on your code.
in one of my apps, webservice-based, i call a login procedure and retrieve a sessionID.
i renew this sessionID every 2h.
if i call a service with an incorrect sessionID i get a certain error and try to login again before trying to call the service anew.
if a sessionID is found on startup (stored in runtimstore) i try to renew its session, if it fails i login and replace it.
02-11-2010 06:46 AM
I am genrating stub through wireless took kit.
Now when i am calling webservice functions, then at server side it is sending different session ID each time.
Do i have to change anything on stub to somehow catch session ID and then send the same session ID each time
02-11-2010 06:58 AM
it depends on your webservice.
on my webservice the sessionID is a parameter on each method i call. it is my duty to put the correct sessionID in there.