Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6.2
-
Component/s: None
-
Labels:None
-
Environment:Java 1.5
JBoss 4.2 GA
Seam 2.0.0 GA
IceFaces 1.6.2 (or 1.7 DR2)
-
ICEsoft Forum Reference:
-
Support Case References:
-
Workaround Exists:Yes
-
Workaround Description:
Description
Using an inputText tag (1*) with the attribute required=true should show a message on the displayed page (h:messages or h:message).
In the log of JBoss, I see the correct message but the message is not rendered in the page.
The behaviour is only by integrating seam. In an Icefaces standalone application the messages are shown.
Furthermore, by changing the icefaces libraries in the icefaces example in the seam distribution, the example has the same behaviour than my application.
The facesmessages are correctly shown when I use the icefaces 1.6.1 libraries !!!
I have a simple example available, which illustrates the problem (http://www2.pch.etat.lu/seamIceTest.tar.gz )
1*
<ice:inputText id="i_characteristique" value="#{cart.caracteristique}" required="true" />
2*
[lifecycle] WARNING: FAcesMessage(s) have been enqueued, bur may have been displayed.
........... Value required .....
Issue Links
- depends on
-
ICE-2312
Javascript failure with partialSubmit used within HTML <fieldset> element
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
See above comments. Since the FacesMessages are rendered properly and the problem with 1.6.2 and 1.7 DR1 and DR2 was really ICE-2312, this issue is resolved.
I was unable to reproduce this problem The FacesMessages do get rendered even though the warning is printed to the server log. The problem with 1.6.2 and 1.7.0 (pre-DR3) has to do with the <fieldset> markup (see ICE-2312). This is now fixed in the 1.6 branch and 1.7 trunk.
This warning has more to do with extra information that is accompanying the FacesMessages information. The actual FacesMessage gets queued properly and rendered, but the extra info (from hibernate from what I can tell), gets queued and it's this that can't be rendered (and that's OK because we don't want it). Components team will have to decide what they want to do about this. I noticed that the Seam team has taken care of this by ensuring that the FacesMessages are included in a particular panel (exadel suite) that renders the message and disregards the extra stuff. Since FacesMessages is a Seam class, there isn't anything we can do about the extra info.
Finally....since all FacesMessages get rendered, I don't see a problem. Perhaps the user can define a particular case when the FacesMessage is not rendered, but the seam-icefaces examples works for all of the above tested ICEfaces releases.
Hi,
Reproducing the problem is quit simple. Download my sample application from (http://www2.pch.etat.lu/seamIceTest.tar.gz ) and extract the tar.gz.
You find an already build ear file at/seamTest/build/jar/
Take this file and deploy it to JBoss 4.2.2 App server.
Go to the url : http://localhost:8080/seamTestWeb/index.seam
A page should be displyed asking you to enter a characteristique. Clicking on the "add to cart gg" button without entering any value produces the problem.
Thanks,
Georges