Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 398 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Forms 11g and Java Web Start using JNLP file

We have this working in a test environment for the most part. Login screen --> list of forms user has access to --> open a form user has access to
The problem is when a user clicks the X in the upper right hand corner of any form, it completely closes the entire applet. User has to relaunch, re-login etc...
In our regular Forms 11g environment not using Java Web Start, when user clicks the X in upper right hand corner, it closes only that form and returns to the previous form. Any ideas how to get that behavior using java web start?
Answers
-
Java Web Start (JWS) was not a certified or supported configuration for running Oracle Forms 11.1.x. Further, v11 is no longer supported. It is recommended that you upgrade to v12 (12.2.1.4) where using JWS is certified/supported and updated code was added to ensure it works as we expect.
Details about the latest version can be found here:
https://www.oracle.com/application-development/technologies/forms/forms.html
You can even try out 12.2.1.4 in Oracle Cloud. This will save you the time of having to download, install, and configure it.
https://cloudmarketplace.oracle.com/marketplace/app/OracleForms
Again, more information about all of this and more, including download and documentation links are provided on the product home page shared above.
Michael Ferrante
Senior Principal Product Manager
Oracle
Twitter: @OracleFormsPM
-
The right point is to change to version 12.2.1.4 ;
if it is not possible, here are tips for Oracle Forms 11g & WebStart that helped me:
https://community.oracle.com/tech/developers/discussion/3592333/forms11g-and-webstart-jnlp
or https://oracle-base.com/articles/11g/oracle-forms-11g-and-java-web-start .
I was able to use Oracle Forms 11g & WebStart in a productive environment for a couple of years.
Hope it helps
-
Thanks for the reply. Upgrading to 12 is not a short term answer for us as hundreds of forms will need to be tested. I'm curious how Forms 11g is no longer supported yet Oracle E-Business Suite still relies on Forms 10g.
-
Thanks. How were you able to get around users clicking the X in the upper right hand corner and that closing the entire applet and the users having to re-login? Training?
-
All versions of Forms older than 12.2.1.3 are no longer entitled to Error Correction. E-Business Suite is treated differently. Bug fixes are provided for EBS on a case by case basis.
Michael Ferrante
Senior Principal Product Manager
Oracle
Twitter: @OracleFormsPM
-
Although this would not be the "right" place to do it, you may be able to catch the MDI being closed in the
POST-FORM
trigger. However, be sure to provide a way out. Meaning, if you block the ability to exit the only way to end the session would be kill the process. If you find this doesn't work, I can tell you that it does work in v12, which becomes yet another reason to upgrade (more bugs fixed and many new features).Edit:
After a brief review, I can see that what you are describing was a bug that was fixed in 12.2.1.0. So, this means that WHEN-WINDOW-CLOSED will not likely work using WebStart in v11. That said, there are likely many things that won't work in v11 with regard to using JWS because many changes were made in order for Forms to fully work as expected/desired in v12. This is why we were not able to support JWS in versions earlier than v12.
Michael Ferrante
Senior Principal Product Manager
Oracle
Twitter: @OracleFormsPM
-
Thanks for the responses. There is a property that can be set in the jnlp file (<param name="separateframe" value="true"/>) that causes our forms application to run in it's own applet window. It's not ideal because there is also a separate blank applet window running but it does allow us to use the X button to close the form and return to the previous form.
-
Assuming I understand what you are trying to do, this will not work in v12. Attempting to do separateFrame=true in v12 while running with JWS will cause the separateFrame request to be ignored.
Michael Ferrante
Senior Principal Product Manager
Oracle
Twitter: @OracleFormsPM
-
It works in v11 even though v11 is not supported