Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3, Mojarra JSF 2.1.21 (new Mojarra warning)
-
Assignee Priority:P2
-
Workaround Exists:Yes
-
Workaround Description:Use Mojarra 2.1.3-2.1.6, or MyFaces 2.1.11.
Description
When running ICEfaces Showcase ace:gMap demos using Mojarra 2.1.21 the following mime type warnings appear in the Tomcat log:
Jun 10, 2013 9:52:37 AM com.sun.faces.context.ExternalContextImpl getMimeType
WARNING: JSF1091: No mime type could be found for file http://maps.googleapis.com/maps/api/js?key=AIzaSyAATyWVqT2qNusNGmcVTyQ0QmymkpU-B5o&libraries=places&sensor=true&libraries=places. To resolve this, add a mime-type mapping to the applications web.xml.
Jun 10, 2013 9:53:10 AM com.sun.faces.context.ExternalContextImpl getMimeType
WARNING: JSF1091: No mime type could be found for file http://maps.googleapis.com/maps/api/js?key=AIzaSyAATyWVqT2qNusNGmcVTyQ0QmymkpU-B5o&libraries=places&sensor=true&libraries=places. To resolve this, add a mime-type mapping to the applications web.xml.
Jun 10, 2013 9:53:31 AM com.sun.faces.context.ExternalContextImpl getMimeType
WARNING: JSF1091: No mime type could be found for file http://maps.googleapis.com/maps/api/js?key=AIzaSyAcAbAa7AL1DLU0785OeWn2byf4XOsm7KM&sensor=true. To resolve this, add a mime-type mapping to the applications web.xml.
Accessing the resource via the JSF ExternalContextImpl is perhaps a hold-over from when the gmap resources were cached on the server and served from there. Can we just change that way that the component accessed the resources?