Using Seam-Config to configure SecurityEventMessages should be a good way...
I'd try to use @Alternative in conjunction with overwriting SecurityEventMessages
enabled = true
enabled = false
Thanks Jan. I've got it working now :-)
The most important hint was the
enabledproperty. I only had a look at CR2 - and there wasn't such a property at that time.
Disabling SecurityEventMessages via seam-config and using my own observer on PostAuthenticate did the trick.
I only had a look at CR2 - and there wasn't such a property at that time.
Yep, Seam 3 is still rather a
fluent API, at least in some places ;-)
Heiko, could you share your beans.xml? I modified mine according to the Seam-Config documentation, but the Login Successful message keeps coming up. Here is my beans.xml:
<beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<!-- this works correctly -->
<!-- event messages keep coming up -->
Not sure about the beans.xml configuration, but you could inject SecurityEventMessages and set enabled false.
The messages will be disabled by default with the upcoming 3.1.0 release.