|summary:||Fix for 11049|
|date:||2009-11-17 15:11:49 UTC (7 years)|
|message:||Fix for 11049
The "user-friendly" context path for launching app clients using Java Web Start does not have a file type as part of the path, but the logic for assigning MIME types to the dynamic content served by the Grizzly adapter used the file type to deduce the MIME type, despite the fact that all dynamic content when created has a MIME type assigned.
This fix uses the assigned MIME type for each dynamic content instance to set its MIME type in the HTTP response which downloads the requested content.
Tests: QL, deployment and ejb and selected webservices devtests; Vince's sample app attached to the issue; Java Web Start tests