Section 102.11.3.1 states that getMimeType from defaultHttpContext should return false so the HttpService implementation will do it's best guess about the mime type of the resource. This is in contradiction with last statement from 102.3 (just before 102.4) that states that getMime should return a reasonable mapping. My suggestion is that this statement from 102.3 should be removed or be in concordance with 102.11.3.1.
On 6/7/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
This issue in the Alliance tracking system will contain any flaws we find about the Http service spec and TCK. I have just managed to run the TCK against the RI. Now, I'm going to figure out how to reduce the testing to only the Http service, and then how to replace the Http service RI with ours, and finally figure out how to build the TCK so I can add more tests... So, Alin (especially) any deviations you find in the org.ungoverned from how you read the spec should be analyzed and possibly brought to the CPEG's attention for clarification followed by more tests for the TCK. Cheers Niclas _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
