You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mike Kienenberger (JIRA)" <de...@myfaces.apache.org> on 2006/08/02 21:49:15 UTC

[jira] Commented: (MYFACES-1372) not shown (-> not working)

    [ http://issues.apache.org/jira/browse/MYFACES-1372?page=comments#action_12425358 ] 
            
Mike Kienenberger commented on MYFACES-1372:
--------------------------------------------

I noticed something that might be related last week.

What happens if you set globalOnly="true"?   Does it then show up?

I tried to find specification documents to determine if global messages should show up when globalOnly isn't specified or if globalOnly="false", but I didn't find anything.

I'm thinking that it's maybe a bug to not show global only messages at all times.


> <h:messages> not shown (-> not working)
> ---------------------------------------
>
>                 Key: MYFACES-1372
>                 URL: http://issues.apache.org/jira/browse/MYFACES-1372
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.1.4-SNAPSHOT
>         Environment: OS= OSX; IDE= Eclipse(3.2) & WTP (1.5) & Java v.5. Using MyFaces 1.1.4 snapshot & Tomahawk 1.1.5 snapshot
>            Reporter: Wolf Benz
>             Fix For: 1.1.5-SNAPSHOT
>
>
> Adding a "global" message in a backing bean goed fine;with the MyFaces log level set to DEBUG, it shows it is indeed added.
> Log extrait:"2006-07-26 10:48:02,296 DEBUG [org.apache.myfaces.shared_impl.util.MessageUtils] - adding message Global Security Test for clientId null"
> Code: I've tried both the Std way & the MyFaces way: (from http://wiki.apache.org/myfaces/Displaying_Errors/Infos/Warnings_in_JSF_Pages)
> FacesContext ctx = FacesContext.getCurrentInstance();
> ctx.addMessage(null, new FacesMessage("Test Summary","Test" ));
> & MessageUtils.addMessage(FacesMessage.SEVERITY_ERROR,"secMsg_test" , null);
> & In the page just this: ( & variations: I've tried to put all before </h:form> but not any order made a difference.
> <t:messages id="errors" errorStyle="error"/>
> </h:form>
> <h:messages id="errors" errorClass="error" />
> Yet, when I ask to show teh source of the actual webpage, I found out it is not renderen. (no component with that ID found) Couldn't believe it so I manually searched for it, knowing its place. But it was true: it's just not on the page. This is particularily weird as -also in debug mode- this fragment passes the revue:
> " <html.HtmlMessages id="errors" forceIdIndex="true" errorClass="NULL" errorStyle="NULL" family="javax.faces.Messages" fatalClass="NULL" fatalStyle="NULL" globalOnly="false" infoClass="NULL" infoStyle="NULL" layout="list" rendered="true" rendererType="javax.faces.Messages" rendersChildren="false" showDetail="false" showSummary="true" style="NULL" styleClass="error" title="NULL" tooltip="false" transient="false" warnClass="NULL" warnStyle="NULL"/>"
> (= in the logs ONLY, NOT in the page)
> Finally: 
> This seems t be an old issue: (April 12, 2005)
> http://mail-archives.apache.org/mod_mbox/myfaces-users/200504.mbox/%3C20050412060343.85397.qmail@web31109.mail.mud.yahoo.com%3E
> <h:messages> is core to JSF. One of the few basic tags. It's strange it suffers from this many bugs. (searched old bugs before posting this one, did my homework ;-)
> Hope someone can rectify it for good. 
> Wolf

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira