[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3116) use a transaction failed event rather than message
2:40 a.m.
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: http://jira.jboss.com/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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:01 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3116) use a transaction failed event rather than message
[ http://jira.jboss.com/jira/browse/JBSEAM-3116?page=comments#action_12417258 ]
Przemyslaw Jaskierski commented on JBSEAM-3116:
-----------------------------------------------
Resolution of JBSEAM-2989 will fix a whole class of Seam's over verbose messages
problems. This one as well.
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: http://jira.jboss.com/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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:55 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3116) use a transaction failed event rather than message
[ http://jira.jboss.com/jira/browse/JBSEAM-3116?page=all ]
Pete Muir closed JBSEAM-3116.
-----------------------------
Resolution: Duplicate Issue
Yeah, lets fix this properly
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: http://jira.jboss.com/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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
3:50 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3116) use a transaction failed event rather than message
[
https://jira.jboss.org/jira/browse/JBSEAM-3116?page=com.atlassian.jira.pl...
]
Sylvain Catudal commented on JBSEAM-3116:
-----------------------------------------
The solution proposed in this JIRA is a lot more to my liking. What's in JBSEAM-2989
looks like a workaround to me.
With this solution, it would be easy to remove whatever default behavior comes with seam
and put in yours or none at all. You could log or you could output different messages
based upon the context. It is way more flexible and should be really easy to implement.
Inserting a blank value in the property file so that the message doesn't show should
only be a temporary solution while waiting for a real fix. It adds a warning and I try to
keep them at a minimum. If there are too many warnings, you stop looking at them and you
miss the important ones.
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: https://jira.jboss.org/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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:11 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-3116) use a transaction failed event rather than message
[
https://jira.jboss.org/jira/browse/JBSEAM-3116?page=com.atlassian.jira.pl...
]
Dan Allen reopened JBSEAM-3116:
-------------------------------
Assignee: Dan Allen
I'm not sure why this was closed. The Seam phase listener shouldn't be adding
messages directly.
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: https://jira.jboss.org/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 2.1.2.CR1
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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:11 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-3116) use a transaction failed event rather than message
[
https://jira.jboss.org/jira/browse/JBSEAM-3116?page=com.atlassian.jira.pl...
]
Dan Allen resolved JBSEAM-3116.
-------------------------------
Fix Version/s: 2.1.2.CR1
(was: 2.1.0.GA)
Resolution: Done
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: https://jira.jboss.org/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 2.1.2.CR1
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3116) use a transaction failed event rather than message
[
https://jira.jboss.org/jira/browse/JBSEAM-3116?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-3116:
-----------------------------------
My comment referred to an early close event. I did resolve this issue the way I had
proposed.
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: https://jira.jboss.org/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 2.1.2.CR1
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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
3:21 p.m.
New subject: [JBoss JIRA] Closed: (JBSEAM-3116) use a transaction failed event rather than message
[
https://jira.jboss.org/jira/browse/JBSEAM-3116?page=com.atlassian.jira.pl...
]
Pete Muir closed JBSEAM-3116.
-----------------------------
use a transaction failed event rather than message
--------------------------------------------------
Key: JBSEAM-3116
URL: https://jira.jboss.org/jira/browse/JBSEAM-3116
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 2.1.2.CR1
Original Estimate: 2 hours
Remaining Estimate: 2 hours
A FacesMessage should not be added by the SeamPhaseListener when the transaction fails.
Instead, it should raise an event that would be observed by a component named
FacesTransactionEvents. That observer would then add the FacesMessage to the response.
This allows developers to override the behavior or perhaps add a JSF or log message.
@see FacesSecurityEvents
--
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
5275
days inactive
5861
days old
7 comments
4 participants
participants (4)
-
Dan Allen (JIRA) -
Pete Muir (JIRA)
-
Przemyslaw Jaskierski (JIRA)
-
Sylvain Catudal (JIRA)