[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly
2:50 p.m.
FacesMessages.instance().addToControl and Datatable do not work properly
------------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables, you
MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:42 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Pete Muir updated JBSEAM-1855:
------------------------------
Fix Version/s: 2.0.0.CR1
Assignee: Pete Muir
Priority: Minor (was: Major)
FacesMessages.instance().addToControl and Datatable do not work
properly
------------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.0.CR1
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:33 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Pete Muir resolved JBSEAM-1855.
-------------------------------
Resolution: Done
Done, please test
FacesMessages.instance().addToControl and Datatable do not work
properly
------------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.0.CR1
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Gavin King reopened JBSEAM-1855:
--------------------------------
Please roll back that change. The contract of addToControl() is very explicit, it is the
id not the client id, check the Javadoc.
FacesMessages.instance().addToControl and Datatable do not work
properly
------------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.0.CR1
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:16 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Pete Muir updated JBSEAM-1855:
------------------------------
Issue Type: Feature Request (was: Bug)
Fix Version/s: (was: 2.0.0.CR1)
Rolled back change and made feature request
FacesMessages.instance().addToControl and Datatable do not work
properly
------------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Assigned To: Pete Muir
Priority: Minor
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Pete Muir updated JBSEAM-1855:
------------------------------
Summary: Provide a FacesMessages.instance().addToControlById() or equivalent (was:
FacesMessages.instance().addToControl and Datatable do not work properly)
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Assigned To: Pete Muir
Priority: Minor
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Pete Muir updated JBSEAM-1855:
------------------------------
Assignee: (was: Pete Muir)
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:23 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Jake C updated JBSEAM-1855:
---------------------------
Attachment: FacesMessages patch.txt
Here is my solution. Instead of adding *ById, I added a new signature that accepts an
index. It simply looks for the first entirely numeric id above a found clientId and
replaces it with the given index.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:45 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=comments#action_12419758 ]
Pete Muir commented on JBSEAM-1855:
-----------------------------------
Can you give an example of how you use this?
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:23 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=comments#action_12419897 ]
Jake C commented on JBSEAM-1855:
--------------------------------
I have a List of items being edited with an <h:inputText id="data"> inside
a <s:decorate> inside an <a:repeat>, with validation done in the backing bean.
When there is an error, I call
facesMessages.addToControlFromResourceBundle("data", rowIndex,
"bundleMsgId", parameters) to have the error message displayed next to the
correct row in the table. As far as I could tell, there is no way to do that with the
current release.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:16 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=comments#action_12419938 ]
Wolfgang Schwendt commented on JBSEAM-1855:
-------------------------------------------
We need something like StatusMessages.addToControl(clientId, severity, msg) rather than
addToControl(componentId, severity, msg).
http://www.seamframework.org/Community/BugInFacesMessagePropagation
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[ http://jira.jboss.com/jira/browse/JBSEAM-1855?page=all ]
Pete Muir updated JBSEAM-1855:
------------------------------
Fix Version/s: 2.1.0.BETA2
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: 2.1.0.BETA2
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[
https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.pl...
]
atait commented on JBSEAM-1855:
-------------------------------
In the 2.0 version we had been using, associating messages with client id was supported by
FacesMessages.addToControl(id, FacesMesssage). Neither FacesMessages nor StatusMessages
supports this in 2.1. As Wolfgang indicates, reconstituting this via StatusMessages would
be a welcomed fix.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: The future
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:44 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[
https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-1855:
------------------------------
Comment: was deleted
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: The future
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[
https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.pl...
]
Stephen Friedrich commented on JBSEAM-1855:
-------------------------------------------
Any news on this?
IMHO this is a bug, not a feature request:
You currently just cannot add a FacesMessage to a specific component and have it survive a
redirect.
After the redirect it will be a global message instead.
(Because FacesMessages.getClientId(String) tries to walk the component tree to determine
the client id for the component id, but that tree is still _empty_ so null is returned.)
We need the client id to correctly add the faces message when rendering the response, but
I don't see how the client id can be computed from the component id when the tree does
not yet exist.
So my conclusion would be that we really need a way to add a message for a _client_ id.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: The future
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:49 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[
https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.pl...
]
Tomasz Szymanski commented on JBSEAM-1855:
------------------------------------------
Agree with Stephen. This should be considered a bug and quite major, cause it's
causing messages not to show at all or show as a global messages.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: The future
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:41 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[
https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.pl...
]
Cloves Almeida commented on JBSEAM-1855:
----------------------------------------
For those struggling with this issue, there's a workaround:
String id =
event.getComponent().getParent().getClientId(FacesContext.getCurrentInstance());
FacesMessage msg = new FacesMessage(FacesMessage.SEVERITY_ERROR, "your message",
null);
FacesContext.getCurrentInstance().addMessage(id, msg);
I second that there should be a FacesMessages.addToControlByClientId, or at least be
better documented.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: The future
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent
[
https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.pl...
]
Moritz Winter commented on JBSEAM-1855:
---------------------------------------
Don't you think the Priority of this should be set to a higher level? For us this is a
showstopper because we can't show validation messages for one or more properties of
mulitple instances of a class. Imho a very often used feature.
Provide a FacesMessages.instance().addToControlById() or equivalent
-------------------------------------------------------------------
Key: JBSEAM-1855
URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
Project: Seam
Issue Type: Feature Request
Components: JSF Integration
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
Priority: Minor
Fix For: The future
Attachments: FacesMessages patch.txt
It is possible do add FacesMessages via the Seam functionality with
FacesMessages.instance().addToControl. In the parameters you have to pass the component
id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In
the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables,
you MUST work with the client-id, the Seam-way with using only the component-id does NOT
work.
Explanation: When using a datatable-tag, you only have one component. The renderer
generates the various rows. In the component-tree there is yet only one component! If you
want to add a FacesMessage to one row, you can only work with client-ids (because you have
to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5414
days inactive
6152
days old
17 comments
10 participants
participants (10)
-
Andy Bosch (JIRA) -
atait (JIRA)
-
Cloves Almeida (JIRA)
-
Gavin King (JIRA)
-
Jake C (JIRA)
-
Moritz Winter (JIRA)
-
Pete Muir (JIRA)
-
Stephen Friedrich (JIRA)
-
Tomasz Szymanski (JIRA)
-
Wolfgang Schwendt (JIRA)