We have found it is sometime necessary to intercept and change the CLSID of the Java version called in the javascript. This can also be achieved using a Browsium ION Custom File. It is also required to amend the security settings in the Deployment.properties file. We also swap out the Java Jinitiator 1.3 jvm.dll and use the 1.4.2_19 version of jvm.dll This can be achieved by using an ION Custom file, this is used to swap the Java dlls to expose the Jinitiator 1.3.1.22 dlls to the application, instead of the highest installed version of Java. Please see ION Can be used to swap out and use Jinitiator 1.3.1.22 instead of the highest version of java installed on the client (say Java JRE 8u121). This can be solved easily using Browsium ION. Would any of you gentle folk be able to help me? I have been perusing the interweb and praying to the Great Pumpkin to find out if there is some way of finding out if this particular setup is going to work without having a bunch of people running around pulling levers, flicking switches and fiddling with knobs. The problem is that the JInitiator executable doesn't want to play nice with IE11. Install multiple versions of the JInitiator onto the desktop Now the kicker, a "tactical solution" has been proposed by a non technical person: There is a Windows 7/IE11 upgrade project underway and the Oracle Forms Apps need to be available on this new desktop setup until the Oracle upgrade has occurred. There is an upgrade project underway and it will eventually be brought up to the latest and greatest version of Oracle etc. I have a client using with the following setup: Has me slightly baffled, what do I change to make it work with the later version of the JRE? I am considering manually changing the code through Chrome to get the page to use a more up to date Java runtime environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |