properties org.jboss.seam.loginFailed (Welcome, username)
Error Message: properties org.jboss.seam.loginFailed (Welcome, username)
Possible Solution:
Possible Solution:
By
default a Seam application (from seam-gen) or copied from a sample, will
display a welcome message on the first post-login screen. To change or remove
this message, edit the messages_en.properties file (and any other translated
message files). Find the entry for:
org.jboss.seam.loginFailed
and either change it to an empty string to remove the message, or to whatever welcome
message you want. Note that when I tried this, the change WAS NOT
hot-deployable. I had to restart the app server to get the message to go away.
The message resource files can be found in rCMS/src (where rCMS is the name of
my project).
Trackbacks
-
6/15/2010 6:32 AM
laurenhepzi wrote:
Know More http://ping.fm/MRPC5



Thanks for the responses. Please note that I have also made changes to messages_en.properties, ensured that the changes were in my deployed .war directory within /jboss/server, and still I receive the entire JSF stack and no noticeable change to the validation message. The only thing I can think of at this point is that at one point we added an
Reply to this
The only thing I can think of at this point is that at one point we added an in our Seam template for a properties file other then messages_en.properties.
Reply to this
This functionality ranges from authentication to batch processing and to validation. For those of you who have used Seam's authentication framework and you know it is extremely easy to use.....
Reply to this
i think many scenarios we may need to format messages on the JSF page using JBoss Seam without calling a backing bean method and One typical example could be displaying a welcome message when the user logs in to the application. This tip explores a component called Interpolator in Seam which helps us the solution..........
http://www.roadsafetyrules.in
Reply to this
0
I had similar problems (this message thing was one of many trust me!) and I just don't use the seam security module anymore. It's not very flexible/extensible, even all the doc say it is (I think it's a lot of self-back-patting by the part of the developer who wrote it all). A similar example I had a bunch of trouble trying to squeeze into this was the handling of a forced password change during the login process. I tore out a lot of my hair before deciding that the whole seam security module just wasn't up to par. It was a bit of a pain, but I have absolutely no regrets. Good luck!
Reply to this
The underlying Identity authentication also fails and adds a StatusMessage. I tried removing the seam generated statusMessage with the following methods, but it doesn't seem to work and shows me 2 different status messages (my custom message, seam generated). What would be the issue here
Reply to this
had similar problems (this message thing was one of many trust me!) and I just don't use the seam security module anymore. It's not very flexible/extensible, even all the doc say it is (I think it's a lot of self-back-patting by the part of the developer who wrote it all). A similar example I had a bunch of trouble trying to squeeze into this was the handling of a forced password change during the login process. I tore out a lot of my hair before deciding that the whole seam security module just wasn't up to par. It was a bit of a pain, but I have absolutely no regrets. Good luck!
Reply to this
well i tried to do it, but i dont know why i am not getting it,can anyone tell me an easier method to do it,plz....
Reply to this