[JBoss JIRA] Created: (SEAMINTL-50) Faces messages should be passed to JSF in the order they were added
by Matija Mazi (JIRA)
Faces messages should be passed to JSF in the order they were added
-------------------------------------------------------------------
Key: SEAMINTL-50
URL: https://issues.jboss.org/browse/SEAMINTL-50
Project: Seam International
Issue Type: Bug
Components: Messages
Affects Versions: 3.0.0.Final
Environment: JBAS7
Mojarra 2.0.4 (FCS b09-jbossorg-4)
Reporter: Matija Mazi
Assignee: Ken Finnigan
Priority: Minor
The MessagesImpl bean does not preserve messages in the order they were added; the order they are output (using <h:messages>) is random.
I've submitted a github pull request; the fix simply uses LinkedHashSet's instead of HashSets. I've tested it, it works for me.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (SEAMINTL-44) BundleTemplateMessage breaks with non-String ResourceBundles
by Nicklas Karlsson (JIRA)
BundleTemplateMessage breaks with non-String ResourceBundles
------------------------------------------------------------
Key: SEAMINTL-44
URL: https://issues.jboss.org/browse/SEAMINTL-44
Project: Seam International
Issue Type: Bug
Components: Messages
Affects Versions: 3.0.0.Final
Reporter: Nicklas Karlsson
Assignee: Ken Finnigan
BundleTemplateMessages has in build()
{code}
try {
text = bundles.get(clientLocale, textKey.getBundle()).getString(textKey.getKey());
} catch (Exception e) {
log.warn("Could not load bundle: " + textKey);
text = textDefault;
}
{code}
which will result in a ClassCastException if the resource is non-string (because ResourceBundle.getString implementation casts getObject to String) and is further translated to a "Could not load bundle" warning followed by the BundleKey being outputted.
Since ResourceBundle.getString is final, there is no way of overloading this behaviour. Using toString on a non-null resource would give some flexibility to this, perhaps.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (SEAMSECURITY-96) Add a new event that gets fired when authorization process has been finished.
by brvno brvnic (JIRA)
Add a new event that gets fired when authorization process has been finished.
-----------------------------------------------------------------------------
Key: SEAMSECURITY-96
URL: https://issues.jboss.org/browse/SEAMSECURITY-96
Project: Seam Security
Issue Type: Enhancement
Affects Versions: 3.0.0.Final
Environment: tomcat 7
Reporter: brvno brvnic
It is impossible to usefully observe the AuthorizationCheckEvent because 'passed' property gets set in one of the observers (namely AuthorizationObserver).
In some containers (tomcat 7 for instance) any observer of AuthorizationCheckEvent gets notified before AuthorizationObserver and therefore cannot use 'isPassed()' method. (Because it always returns false).
Please add one more event at the end of the authorization process which clients of the library can observe in a useful manner. That event could contain an information about which security bindings were checked, and the result of that check. Please make this event immutable.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months