Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Java Bug 7171412, awt choice

Hello everybody,
we use a ten year old software in our department (health sector) which won't be updated any more.
Now with Java 1.7.0_25 (and former Java 1.7) we have problems with the known bug 7171412 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7171412).
This bug will not be fixed until Java 1.8 (release date ist spring 2014) and there is no workaround in code.
The only workaround is to select any other item from the Choice and then reselect the previously selected item in order for the ItemStateChange Event to be fired correctly.
This is not a real acceptable solution to our problem. We aren't able to wait one whole year for a solution in code.
By the way, there is already a Java 1.8 early access version (which we aren't allowed to use because of CERT and security).
Why Oracle doesn't put it into a patch? We really need a solution very soon.
Does anybody have any tips for us?
Thanks, Carina
Answers
-
Revert back to a Java version supported by your software, and don't ever move out.