Skip to main content

Firefox and JInitiator crashes

Today I discovered that Firefox crashes when I started up an Oracle Forms application using JInitiator. One thing I noticed that two JVM's were started (two icons showed up in the taskbar). After switching off Java inside Firefox (via Tools->Options->Content) everything works fine. So no need for IE anymore...

Comments

Takis said…
I am trying to get Firefox and Jinitiator to work on Vista but it keeps complaining about a missing plugin. Any ideas?
Roel said…
I don't have a Vista PC, but from what I understood from Oracle, JInitiator will not be certified on Vista. You should use Suns JVM instead.
aims said…
Hi Roel,
i am vista user. can u tell me i can i make my PC work for Oracle application without useing JInitiator

Amit
Roel said…
As you can find on http://www.oracle.com/ technology/products/forms/ htdocs/10gR2/clientsod_forms10gR2.html :

JInitiator is known to not work with Vista and Sun is not planning to support 1.3 on Vista. Oracle therefore have no plans to certify JInitiator with Vista.Vista users should be steered towards Sun's plug-in 1.5 once it is certified. That is planned for 10.1.2.3.

So you should try using Suns JVM instead of JInitiator (I didn't try it yet, because I don't have Vista).
HTH
Roel said…
And using JVM instead of JInitiator needs a change on the applicition server config files (and not on the PC of th e end user).
jkwong111 said…
Thanks for the tip! It works and saved me A LOT of time!
Ganesh said…
What change is required on the applicition server config files . Could you please explain so I can ask my DBA's to it ?

Ganesh
Ganesh said…
what changes are necessary in the server config to make Oracle application work wiht Vista ?
Roel said…
Ganesh,

You have to modify the formsweb.cfg file. See this for the details.

HTH
Roel
Anonymous said…
Hi there!

I Managed to get JVM to work for Vista by editing formsweb.cfg and change the settings of the forms server to auto download the correct plugins. My article is in dutch, you can read it here. Fot the non-dutch readers: at the bottom of the document there are some links to english articles.

Good luck!
Anonymous said…
nice post

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function