JDK-8090338 : Should throw UnsupportedOperationException in ES2 pipeline initialization
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 7u6
  • Priority: P5
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2012-06-08
  • Updated: 2018-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8102203 - ES2RTTexture.readPixels allocates new byte buffer for each frame
Description
The code added to fix RT-21740 assumes a little-endian architecture. We should throw an exception from the ES2 pipeline initialization code if we encounter a big-endian byte order until such time as we are ready to deal with it. Something like

    if (ByteOrder.nativeOrder() == ByteOrder.BIG_ENDIAN) {
        throw new UnsupportedOperationException("...");
    }
Comments
Suggestion from Jim: A compile time ifdef would be lower overhead, but if that check is only done in pipeline setup, then that isn't an issue. On the other hand, if we later delete readPixels() someone might forget why we have that restriction and spend a lot of time trying to figure out who and what thought we might need to run on LITTLEENDIAN. I see you filed a Jira issue - maybe that is enough (i.e. change it to simply be a catalog of all endianness issues in ES2N and it will stay open until we either fix them or get rid of them)...? If we do throw the exception for completeness, then a comment should reference the bug that lists the issues...
08-06-2012