ICEfaces
  1. ICEfaces
  2. ICE-6914

Eliminate JSF warning messages when creating JSF resources with unknown file extension

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.2
    • Fix Version/s: 2.1-Beta, 3.0, EE-2.0.0.GA_P01
    • Component/s: None
    • Labels:
      None
    • Environment:
      server

      Description

      JSF logs warning messages when resources are created with an unknown file extension. These messages appeared after a fix for ICE-6851 was applied:

      com.sun.faces.context.ExternalContextImpl getMimeType
      WARNING: JSF1091: No mime type could be found for file listen.icepush. To resolve this, add a mime-type mapping to the applications web.xml.

      com.sun.faces.context.ExternalContextImpl getMimeType
      WARNING: JSF1091: No mime type could be found for file create-push-id.icepush. To resolve this, add a mime-type mapping to the applications web.xml.

      com.sun.faces.context.ExternalContextImpl getMimeType
      WARNING: JSF1091: No mime type could be found for file notify.icepush. To resolve this, add a mime-type mapping to the applications web.xml.

      com.sun.faces.context.ExternalContextImpl getMimeType
      WARNING: JSF1091: No mime type could be found for file add-group-member.icepush. To resolve this, add a mime-type mapping to the applications web.xml.

      com.sun.faces.context.ExternalContextImpl getMimeType
      WARNING: JSF1091: No mime type could be found for file remove-group-member.icepush. To resolve this, add a mime-type mapping to the applications web.xml.

      Even when the mime-type was provided by calling ResourceHandler.createResource(resourceName, libraryName, contentType) the warnings are still shown.

        Activity

        Hide
        Mircea Toma added a comment -

        The warnings should not be shown by JSF if the resource content type is provided. We need to record a bug in the JSF bug tracking system. Also attach a patch to the JSF bug.

        Show
        Mircea Toma added a comment - The warnings should not be shown by JSF if the resource content type is provided. We need to record a bug in the JSF bug tracking system. Also attach a patch to the JSF bug.
        Hide
        Mircea Toma added a comment -

        In the mean time we need to find a workaround for this issue.

        Show
        Mircea Toma added a comment - In the mean time we need to find a workaround for this issue.
        Hide
        Mircea Toma added a comment - - edited

        As a workaround added known file extensions to the created resources, this way the JSF and the servlet container will easily find the matching mime-type. For example listen.icepush resource now becomes listen.icepush.xml. Each file extension corresponds to resource's response content type. In the case of listen.icepush the response contains the DOM updates as XML data.
        Renamed also the dummy resource files to correspond to the new resource names.

        Show
        Mircea Toma added a comment - - edited As a workaround added known file extensions to the created resources, this way the JSF and the servlet container will easily find the matching mime-type. For example listen.icepush resource now becomes listen.icepush.xml. Each file extension corresponds to resource's response content type. In the case of listen.icepush the response contains the DOM updates as XML data. Renamed also the dummy resource files to correspond to the new resource names.
        Hide
        Mircea Toma added a comment -
        Show
        Mircea Toma added a comment - Recorded JSF issue here: http://java.net/jira/browse/JAVASERVERFACES-2103

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Mircea Toma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: