I am calling PrintService.getSupportedDocFlavors() with respect to each print service available on my Solaris system and I am getting a set of doc flavors. I am calling PrintService.isDocFlavorSupported() on the same print service by passing each of the flavors returned above. I am surprised to see 3 new flavors being returned by getSupportedDocFlavors() but isDocFlavorSupported() returns FALSE for these flavors with the same print service. Hence there is a conflict between these 2 methods. This must be fixed for Mustang.

This is reproducible only on the PIT build given below and not reproducible on Mustang-b55. This is reproducible only on SolarisSparc - NonCUPS and not reproducible on CUPS/Win32. I have not tested on lprng-linux yet. This is a regression introduced in the current PIT build:

java version "1.6.0-internal"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-internal-tdv_06_Oct_2005_00_47-b00)
Java HotSpot(TM) Server VM (build 1.6.0-ea-b54, mixed mode)

Here are the newly shown flavors:
text/plain; charset="iso646-us"; class="[B"
text/plain; charset="iso646-us"; class="java.io.InputStream"
text/plain; charset="iso646-us"; class="java.net.URL"

I have attached a sample test. Run the same test and it would highlight the flavors that are in conflict, for each of the print services available on the system.