-
1. Re: Bug in FacesMessage propagation
wschwendt Jun 13, 2008 5:44 PM (in response to wschwendt)To clarify, I was referring to Seam 2.1 SVN current trunk
-
2. Re: Bug in FacesMessage propagation
atait Nov 18, 2008 3:52 PM (in response to wschwendt)Does the Seam team acknowledge this shortcoming? There doesn't appear to be an elegant way to refactor this aspect of our code to support an upgrade to 2.1. Less than elegant strategies are available...
Allen
-
3. Re: Bug in FacesMessage propagation
joblini Nov 18, 2008 5:33 PM (in response to wschwendt)Why do you think this is related to upgrading to Seam 2.1?
There has been an open JIRA on this for quite some time, you can vote for it here:
-
4. Re: Bug in FacesMessage propagation
atait Nov 19, 2008 1:25 PM (in response to wschwendt)Becasue earlier versions supported this with Seam's:
- FacesMesssages.addToControl(id, facesMessage);
This method was removed, not depricated, from the API across the upgrade.
I was not aware of the jira entry. Will add my vote now.
Thanks
-
5. Re: Bug in FacesMessage propagation
atait Nov 19, 2008 1:32 PM (in response to wschwendt)Well that jira issue is similar but does not address specifically what this thread refers to IMO. The capability was available in earlier versions of Seam. We have been using this capability to propagate messages across redirects, has been working fine.
The 2.1 API no longer supports the method I reference above, not in FacesMessages, not in StatusMessages ...
Allen
-
6. Re: Bug in FacesMessage propagation
atait Nov 20, 2008 2:29 AM (in response to wschwendt)My mistake. That JIRA issue appears to represent this topic. I have added my vote.
Thanks
-
7. Re: Bug in FacesMessage propagation
stephen Jan 2, 2009 2:02 AM (in response to wschwendt)Well, if you study the Jira issue carefully, yes, it covers this problem. But the actual problem is more severe than it appears from reading the jira issue:
You cannot add a faces message to a control and have it survive a redirect!
Somebody please correct me if I failed to see the obvious solution/workaround.