MIME type resolution doesn't work in pax-web-jetty [PAXWEB-317]

[ops4j-issues]

Raul Kripalani created PAXWEB-317

MyFaces does some clever magic so that when a browser requests a resource, it will return different types of InputStreams depending on the MIME type of the resource that was requested. If it is a file, it will return a standard InputStream, but if it is a CSS file, it will return a special stream called "ValueExpressionFilterInputStream", which preprocesses the CSS file and resolves all EL expressions into an actual result.

The problem is that the current version of pax-web is unable to resolve MIME types from SContext.getMimeTypes() because if the mime type is not defined in the app's web.xml, it will fall back to the HttpContext (Pax Web's DefaultHttpContext) which ultimately always returns null.

---

Affects: 1.0.7, 1.1.1, 2.0.0 Fixed in: 1.0.8, 1.1.2, 2.0.0 Votes: 0, Watches: 0

---

Referenced issues

relates to:

• 660 - Re-work the MIME resolution logic [PAXWEB-318]

[ops4j-issues]

Raul Kripalani commented

SContext.getMimeTypes() should delegate to Jetty which already provides MIME type resolution functionality.

[ops4j-issues]

Raul Kripalani commented

Fixed. Commits:

• master: d6c72df942260c31946520408d23cfeccd722116
• 1.1.x: 616dc50ee878c2dfdc696b2de6ca15655ffb3678
• 1.0.x: d030ae90706f11e705408e660ed5d4f66301248b

[ops4j-issues]

Raul Kripalani commented

Going forward, the MIME type resolution mechanism should be reworked