[ http://issues.apache.org/jira/browse/MYFACES-678?page=comments#action_12356314 ]
Martin Marinschek commented on MYFACES-678: ------------------------------------------- I just checked the head version - in this version, this is correctly defined, as far as I can see. Can you try it out with the nightly build? regards, Martin > Can't find "org.apache.myfaces.Message" when HtmlMessageTag.getRendererType() > is invoked > ---------------------------------------------------------------------------------------- > > Key: MYFACES-678 > URL: http://issues.apache.org/jira/browse/MYFACES-678 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: 1.1.0, Nightly, 1.1.1 > Environment: MyFaces 1.1.0; Tomcat 5.5.9; Java SE 5.0; Mac OS X 10.4 > Reporter: Mason Hsieh > Assignee: Martin Marinschek > Priority: Critical > > When the tag: <x:message> or <t:message> is invoked, exception thrown as > followed: > javax.faces.FacesException: Undefined component type > org.apache.myfaces.HtmlMessage > at > org.apache.myfaces.application.ApplicationImpl.createComponent(ApplicationImpl.java:390) > at > javax.faces.webapp.UIComponentTag.createComponentInstance(UIComponentTag.java:448) > at > javax.faces.webapp.UIComponentTag.findComponent(UIComponentTag.java:391) > at > javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:219) > at > org.apache.jsp.customers_jsp._jspx_meth_x_message_0(org.apache.jsp.customers_jsp:525) > : > It may come from the class: > org.apache.myfaces.taglib.html.ext.HtmlMessageTag.getRendererType(). > The returned type is "org.apache.myfaces.Message". > The workaround is to use <h:message> instead of <x:message> or <t:message> -- 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
