Hello Simon, In the actual urgency I need to show this up on next tuesday and I would like to do something that could bring back that feature.
I preffer to display the error messages in the top of the page, not close to each field itself as it is better for generalizing the application, specially in my case that there are a lot of screens that does CRUD and takes some time to complete. After finishing this task and setting up a new deadline I think I am going to work into a better sollution, I will try using a PhaseListener as you've suggested and see if it works. Many thanks for your time and help. It is really much appreciated. Best Regards, Ernani Simon Kitching-3 wrote: > > Simon Kitching wrote: >> Hi Ernani, >> >> If your application always uses the same values for the f:loadBundle tag >> attributes (ie basename and var are always the same) then you might be >> able to work around this problem with a hack: write a PhaseListener, >> then on post-restore-view, do this: > > Hmm..if ResourceBundle is thread-safe then you could even store the map > wrapper for it into the application scope on webapp startup. The > javadocs for ResourceBundle don't state whether it is threadsafe or not > though. > > Note that these hacky solutions aren't a good choice for a large and > complex JSF webapp..in those cases a proper fix would be preferable. > > Cheers, > > Simon > > -- View this message in context: http://www.nabble.com/f%3Aattribute-in-phaselistener-tf3586393.html#a10091097 Sent from the MyFaces - Users mailing list archive at Nabble.com.
