[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2678) improve docs for conversation propagation
by Martin Trummer (JIRA)
improve docs for conversation propagation
-----------------------------------------
Key: JBSEAM-2678
URL: http://jira.jboss.com/jira/browse/JBSEAM-2678
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation Issues
Environment: n.A.
Reporter: Martin Trummer
following points should be emphasized in the docs:
* the fact, that ending a conversation demotes the long-running conversation to a temporary conversation should be emphasized in the docs or explained in more detail
* the difference between ending a conversation and ending a conversation before-redirect should also be explained in more detail
* the docs should mention, that any facesMessages are lost, when you end the conversation and use before-redirect=true (and maybe how to work around this)
discussion can be found in the forum
I will attach a text file with a draft, of what these improvements could be (hope this helps)
--
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
14 years, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2257) Raise a session expired and new session event on occurence
by Jacob Orshalick (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
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
14 years, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1875) Rework configuration chapter
by Pete Muir (JIRA)
Rework configuration chapter
----------------------------
Key: JBSEAM-1875
URL: http://jira.jboss.com/jira/browse/JBSEAM-1875
Project: JBoss Seam
Issue Type: Task
Components: Documentation
Affects Versions: 2.0.0.BETA1
Reporter: Pete Muir
Fix For: 2.0.0.GA
Rework configuration chapter to make it a generic discussion of configuring and packaging Seam applications. Move platform specific stuff to platform specific chapter.
i.e.
25 Configuring & Packaging Seam Applications
25.1 Basic Seam Configuration
25.1.1 Integrating Seam with JSF and the Servlet Container
25.1.2 Using Facelets
25.1.3 Seam Resource Servlet
25.1.4 Seam Filter
25.1.5. Integrating Seam with your EJB container
25.2 Seam Applications in a JEE 5 environment
25.3 Seam Applications in a J2EE environment
25.4 Seam Applicaitons in a JSE environment
* Move JBPM configuration to JBPM chapter
* Move JBoss AS stuff to new JBoss AS chapter
* Move JBoss Embedded stuff to new JBoss Embedded Chapter
26 Seam on JBoss AS
26.1 Seam on JBoss AS 4.0
* Includes stuff on install JSF 1.2 from Chapter 2
26.2 Seam on JBoss AS 4.2
27 Seam with JBoss Embedded
28 Seam on OC4J
29 Seam on Glassfish
* Needs writing!
--
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
14 years, 6 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3159) Debug/development mode control
by Pete Muir (JIRA)
Debug/development mode control
------------------------------
Key: JBSEAM-3159
URL: http://jira.jboss.com/jira/browse/JBSEAM-3159
Project: Seam
Issue Type: Task
Components: Tools
Reporter: Pete Muir
Priority: Critical
Fix For: 2.1.0.BETA2
Currently we have a very overloaded system which is hard to use:
1) debug flag is used to control parsing of hot-deploy (/dev) which is odd
2) to view the debug page at all you must both include jboss-seam-debug.jar and enable debug mode in components.xml. Further, if you do this, then the debug page handler is installed, which screws with the exception handling.
I propose that by simply including jboss-seam-debug.jar you get
1) hot deployment enabled
2) use of the debug page by calling /debug.seam BUT not as a redirect off the exception handler
and, further, by
<exception:exceptions enable-debug-page="true" /> (better ideas for attribute name?)
you can automagically redirect to the debug page when an exception occurs. The default for this is false, and this should be set in seam-gen (the seam-gen app should include a link to debug.seam in perhaps its footer)
--
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
14 years, 6 months