Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.3
-
Fix Version/s: 3.3
-
Component/s: QA, Sample Apps
-
Labels:None
-
Environment:Icefaces3 trunk revision# 33386
Server: tomcat6
Browser: All
-
Assignee Priority:P1
-
Workaround Exists:Yes
-
Workaround Description:Workaround is to use MyFaces JSF or Mojarra JSF 2.1.17, or just ignore the warnings in the logs.
Description
Warning still exists when navigating in the showcase application (clicking on demo links):
WARNING: JSF1091: No mime type could be found for file http://wiki.icefaces.org/display/ICE/AutoCompleteEntry.
To resolve this, add a mime-type mapping to the applications web.xml.
Note: By looking at previous tomcat logs, it seems that this warning only occurs when Mojarra 2.1.18 libs are being used.
WARNING: JSF1091: No mime type could be found for file http://wiki.icefaces.org/display/ICE/AutoCompleteEntry.
To resolve this, add a mime-type mapping to the applications web.xml.
Note: By looking at previous tomcat logs, it seems that this warning only occurs when Mojarra 2.1.18 libs are being used.
Issue Links
- blocks
-
ICE-9097
Add support for different types of URL encodings in ace:menuItem
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Arturo Zambrano [ artzambrano ] | |
| Fix Version/s | 3.3 [ 10370 ] | |
| Affects Version/s | 3.3 [ 10370 ] | |
| Assignee Priority | P2 [ 10011 ] |
| Assignee Priority | P2 [ 10011 ] | P1 [ 10010 ] |
| Summary | Icefaces3 Regressions - sample - showcase - No Mime type could be found for file | WARNING: JSF1091: No mime type could be found for file logged by showcase with ace:fileEntry demo |
| Workaround Description | Workaround is to use MyFaces JSF or Mojarra JSF 2.1.17, or just ignore the warnings in the logs. | |
| Security | Private [ 10001 ] | |
| Workaround Exists | Yes [ 10007 ] |
Marking this issue as Won't Fix.
Created ICE-9097 to proceed with the suggested improvements.
Show
Arturo Zambrano
added a comment - Marking this issue as Won't Fix.
Created ICE-9097 to proceed with the suggested improvements.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Won't Fix [ 2 ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #35622 | Mon May 27 12:22:34 MDT 2013 | art.zambrano | |
| Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/samples/showcase/showcase/src/main/webapp/resources/templates/content-template.xhtml
|
| Status | Resolved [ 5 ] | Closed [ 6 ] |
After moving to Mojarra 2.1.18, a warning message started to appear in the server console every time a link was rendered in an ace:menuItem component. The reason is that the URL specified in the 'url' attribute of said component is passed to ExternalContext.encodeResourceURL() every time. So, it is assumed that the URL is a resource or an action in the application, and this method tries to find a MIME type. When it doesn't find a MIME type (as in the case of most external URLs), it produces the warning message.
It was found that this behaviour is not exclusive to ace:menuItem. The exact same thing happens with the standard h:outputLink component (Mojarra), since it also calls ExternalContext.encodeResourceURL(), as can be read in the TLD documentation page for this component. Furthermore, this situation only occurs when using Mojarra. The warning message is not printed when using MyFaces, and the documentation for its h:outputLink component doesn't mention anything about calling ExternalContext.encodeResourceURL().
Therefore, this is an issue within Mojarra. In order to avoid this in the future, we should add support to ace:menuItem for different types of URL encodings, inclluding the case where no encoding is needed.