Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Invalid
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Incident Severity: Severe: Errors that disable major functions from being performed
Contact Name: Andrew White
Email Address: amwhite@bop.gov
Telephone Number: 202-514-4844
Company Name: BOP
This customer is supported: Yes
Agreement Number: 0
ICEsoft Product: ICEfaces
Product Version Number: 2
Application Server: Apache Tomcat
Development IDE: Eclipse
Problem Description: Application level validation messages aren't displaying. Error received: "FacesMessage(s) have been enqueued, but may not have been displayed." This seems to indicate that the element in error cannot be found on the page. When inspecting the element, I found the id contained extra stuff, even though I assigned it a simple "selected". I referenced it by "formName:selected", but to actually get the FacesMessage to work, I had to reference it by "formName:j_idt25:0:selected", which I found using tools to inspect the element.
Contact Name: Andrew White
Email Address: amwhite@bop.gov
Telephone Number: 202-514-4844
Company Name: BOP
This customer is supported: Yes
Agreement Number: 0
ICEsoft Product: ICEfaces
Product Version Number: 2
Application Server: Apache Tomcat
Development IDE: Eclipse
Problem Description: Application level validation messages aren't displaying. Error received: "FacesMessage(s) have been enqueued, but may not have been displayed." This seems to indicate that the element in error cannot be found on the page. When inspecting the element, I found the id contained extra stuff, even though I assigned it a simple "selected". I referenced it by "formName:selected", but to actually get the FacesMessage to work, I had to reference it by "formName:j_idt25:0:selected", which I found using tools to inspect the element.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Your right on. Should have notice that myself. Thanks for the assistance.
Andrew
Show
Tyler Johnson
added a comment - Your right on. Should have notice that myself. Thanks for the assistance.
Andrew
No problem, glad I could help. I'll go ahead and close this case.
Thanks,
Arran
Show
Tyler Johnson
added a comment - No problem, glad I could help. I'll go ahead and close this case.
Thanks,
Arran
Marking as Closed / Invalid as part of legacy ICEfaces ICE / Compat component JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.
Show
Ken Fyten
added a comment - Marking as Closed / Invalid as part of legacy ICEfaces ICE / Compat component JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.
Hi Andrew,
I assume you are calling FacesContext.addMessage() to display your FacesMessage?
The addMessage method uses the client id of the component when adding the message. This client id is built up of the different container/parent elements for that component. It starts with the form component and then goes down the component tree.
From the looks of the client id that is working, the component you are trying to reference is inside a tab set or a dataTable, which would be why the extra id sections are added.
This is the normal JSF behavior. Let me know if you have any questions.
Thanks,
Arran