[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2257) Raise a session expired and new session event on occurence
1:22 a.m.
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Priority: Minor
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
12:49 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12388057 ]
Jacob Orshalick commented on JBSEAM-2257:
-----------------------------------------
It would be nice if the event was initiated after the RESTORE_VIEW once the conversation
has been initialized. This would allow the FacesMessages component to be used to easily
add a message for user notification, i.e.
@Observes("org.jboss.seam.sessionExpired")
public void sessionExpired(String message)
{
FacesMessages.instance().add("User session expired");
}
The current workaround is described at:
http://solutionsfit.com/blog/2007/11/16/session-expired-messages-using-se...
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Priority: Minor
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
5:59 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Shane Bryzak reassigned JBSEAM-2257:
------------------------------------
Assignee: Shane Bryzak
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
8:30 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Pete Muir updated JBSEAM-2257:
------------------------------
Fix Version/s: 2.0.x
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
5:49 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394185 ]
Florian Fray commented on JBSEAM-2257:
--------------------------------------
This could be implemented quite easily via the class org.jboss.seam.contexts.Lifecycle .
Add a line "Events.raiseEvent("org.jboss.seam.newSession")" around ll.
188 (refering to 2.0.0.GA) and
"Events.raiseEvent("org.jboss.seam.sessionExpired")" around ll. 238.
Well the Seam-Devs know where to add this, but maybe you'd like to patch this class
before it is released.
IMHO this is a quite reasonable request and would like to have it. We had to do sth.
similar to keep track of destroying the session.
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
8:02 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394209 ]
Pete Muir commented on JBSEAM-2257:
-----------------------------------
The point is to raise an event on session expiry, and not when the user closes the session
themselves. I don't think your proposal achieves this?
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
11:10 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394270 ]
Florian Fray commented on JBSEAM-2257:
--------------------------------------
Pete, the Lifecycle.beginSession and .endSession is also triggered by the SeamListener,
which is implementing javax.servlet.http.HttpSessionListener.
So it is reacting precisely on Session-creation and -destruction.
You can approve this by following the code in org.jboss.seam.servlet.SeamListener.
Here's the related code for comfort-reasons:
org.jboss.seam.servlet.SeamListener
###
...
public void sessionCreated(HttpSessionEvent event)
{
ServletLifecycle.beginSession( event.getSession() );
}
public void sessionDestroyed(HttpSessionEvent event)
{
ServletLifecycle.endSession( event.getSession() );
}
...
###
org.jboss.seam.contexts.ServletLifecycle
###
...
public static void beginSession(HttpSession session)
{
Lifecycle.beginSession( new ServletSessionMap(session) );
}
public static void endSession(HttpSession session)
{
Lifecycle.endSession( new ServletSessionMap(session) );
}
...
###
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
2:44 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394304 ]
Jacob Orshalick commented on JBSEAM-2257:
-----------------------------------------
What Pete is saying holds true here...
By simply placing the event in the beginSession and endSession, you cannot achieve the
purpose of this request. Essentially the goal of this request is to raise an event when
the session expires while a user is still active within the application (mainly for
messaging purposes). The approach you suggest would raise the event always when a new
session is started. The checks against the session id allow us to differentiate between a
new session:
- where the browser was closed (the user expired the session) = new session and no session
id (cookie gone)
- the session expired from user inactivity = new session and session id still present
(cookie still present)
Another difficulty here is the message as described in the first comment. The timing of
the event will be critical to ensure that the FacesMessages component exists in the
context.
I will try to create a patch in the next few weeks (for this and a few other JIRAs
I've requested). Been very busy with work lately ;)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
4:56 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394329 ]
Florian Fray commented on JBSEAM-2257:
--------------------------------------
Okay, I've understood you want to check whether the session-id sent is still valid or
not.
We've used this information (session created / session destroyed) differently, as we
wanted to keep track of the currently logged in users.
Basically we've used the events org.jboss.seam.postAuthenticate and
org.jboss.seam.loggedOut, but we also needed an event raised when the session expired,
i.e. due to inactivity.
The code described just shows you that an invalid session-id has been used, but you
won't really get the event at the time it expired, but with the next request (which
could be days after the session expired).
The nasty drawback is that if the user does not send a request to the application again,
you won't be able to recognize the session has expired.
IMHO this makes a huge difference. For our usecase it is crucial to get an event as soon
as the session expired, not after the next request.
What about a third event, so we'd have:
"org.jboss.seam.expiredSession" (or sessionExpired)
"org.jboss.seam.newSession"
"org.jboss.seam.destroyedSession"
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
5:56 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394346 ]
Pete Muir commented on JBSEAM-2257:
-----------------------------------
Sure.
Thats what we've been trying to get you to understand - the difference between session
expiry and destroying the session.
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
6:03 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=comments#action_12394349 ]
Jacob Orshalick commented on JBSEAM-2257:
-----------------------------------------
Your request sounds reasonable to me. I am +1 on the third event. I've seen requests
for this on the forum as well for performing cleanup and auditing tasks (and I could see
myself needing this at some point in the future ;-) ).
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.0.x
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
1:10 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Pete Muir updated JBSEAM-2257:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.x)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.1.0.GA
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
4:33 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Jacob Orshalick updated JBSEAM-2257:
------------------------------------
Attachment: JBSEAM-2257.patch
Relies on JBSEAM-2505 to work within a servlet JSF request. The requested third event
will be a separate patch (perhaps a different JIRA?).
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.1.0.GA
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
7:59 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Norman Richards updated JBSEAM-2257:
------------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.A1)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.1.0.GA
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
12:29 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Pete Muir updated JBSEAM-2257:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.BETA1)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.1.0.GA
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
5:14 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[ http://jira.jboss.com/jira/browse/JBSEAM-2257?page=all ]
Pete Muir updated JBSEAM-2257:
------------------------------
Fix Version/s: 2.1.0.BETA1
(was: 2.1.0.GA)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: http://jira.jboss.com/jira/browse/JBSEAM-2257
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 2.1.0.BETA1
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
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
1:31 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Pete Muir reassigned JBSEAM-2257:
---------------------------------
Assignee: Jacob Orshalick (was: Shane Bryzak)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: The future
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:27 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Pete Muir commented on JBSEAM-2257:
-----------------------------------
Jacob, do you want to apply this?
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: The future
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:34 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Jacob Orshalick updated JBSEAM-2257:
------------------------------------
Fix Version/s: 2.1.1.CR1
(was: The future)
Yes, I'll get it in for 2.1.1.
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: 2.1.1.CR1
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Shane Bryzak updated JBSEAM-2257:
---------------------------------
Fix Version/s: 2.1.1.CR2
(was: 2.1.1.CR1)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: 2.1.1.CR2
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-2257:
------------------------------
Fix Version/s: 2.1.2.CR1
(was: 2.1.1.CR2)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: 2.1.2.CR1
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-2257:
------------------------------------
Fix Version/s: 2.1.2.GA
(was: 2.1.2.CR1)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: 2.1.2.GA
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:58 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-2257:
------------------------------------
Fix Version/s: 2.1.2
(was: 2.1.2.CR2)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: 2.1.2
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:58 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-2257:
------------------------------------
Fix Version/s: 2.2.0.CR1
(was: 2.1.2)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: 2.2.0.CR1
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:56 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-2257) Raise a session expired and new session event on occurence
[
https://jira.jboss.org/jira/browse/JBSEAM-2257?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-2257:
------------------------------------
Fix Version/s: The future
(was: 2.2.1.CR1)
Raise a session expired and new session event on occurence
----------------------------------------------------------
Key: JBSEAM-2257
URL: https://jira.jboss.org/jira/browse/JBSEAM-2257
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.0.GA
Reporter: Jacob Orshalick
Assignee: Jacob Orshalick
Priority: Minor
Fix For: The future
Attachments: JBSEAM-2257.patch
You have to make some assumptions here, but you can basically notify the user when the
server session has ended with the following in a PhaseListener:
Code:
@Observer("org.jboss.seam.beforePhase")
public void beforePhase(PhaseEvent event)
{
if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
{
HttpServletRequest request =
(HttpServletRequest) FacesContext.getCurrentInstance()
.getExternalContext().getRequest();
if(request.getRequestedSessionId() != null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.sessionExpired");
...
Based on general cookie settings this will raise the event when the user still has the
browser window open, the http session expired, and the user tries to access the app. If
the user closes and reopens the browser to start the application, the event will not be
raised. This of course makes the assumption that cookies expire when the browser session
is ended (which is generally the case).
The org.jboss.seam.newSession event would simply change the condition to:
if(request.getRequestedSessionId() == null
&& request.getSession().isNew())
Events.instance().raiseEvent("org.jboss.seam.newSession");
This is generally useful for user notification on the login screen. Please see the forum
reference for more information. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5308
days inactive
6072
days old
24 comments
5 participants
participants (5)
-
Florian Fray (JIRA) -
Jacob Orshalick (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)
-
Shane Bryzak (JIRA)