If the user chooses the no then the user s session is made InActive in the Cache Manag

er s Object Map and the user is notified to login using other user credentials.
Are the classes which are mentioned in the sequence diagrams exists already?
is this cache manager service is already implemented or under design only?
How does the Session Manager implements the creation of jsessionid?
What happens, when a user sends the jsession id after the timeout interval, how
is it implemented such that it can identify whether user accessed after the time
out period?
EhCache mechanism of the Spring Framework
The session ID and the user preferences are sent across to the business tier via
the remote object calls.
user preferences - ? are these part of map that is being stored in cache?
how the jsession id is created, is there any logic to create or httpsession's se
ssion id is being used?
1) How would the CacheManager service usage reflect in case of Clustered environ
ment? Is the Cache is being replicated and can be synchronized?
2) Do you know that is there any chances of the users logging in can have dynami
c IP?
3) How is the session state invalidated with the Cache Manager service?
4) For handling the heartbeat requirement - Need to add the field for the user l
ast interacted time.
5) I could see that web services are mentioned in the application for login, sec
urity, session management, cachemanager? Need some clarity on the usage of web s
ervice vs web application here in this scenario and also overall in the architec
ture?
6) Already we are using JBoss Cache, why don t we leverage that JBoss Cache for th
is purpose also, instead of using ehcache?
I heard from you that already some discussions went on related to using the data
base implementation for this Vs cache implementation. Would like to know the inf
ormation which is already discussed regarding this.