EnterpriseOne Tools Release 8.97 & 8.98 Not Compatible With FireFox 3

Read Time:1 Min, 40 Sec

In doing some last minute testing with EnterpriseOne Tools Release 8.97.2.0, I found that the applications do not render in FireFox 3. The error that I received in the WAS log is:

VTFormRenderAdaptee: renderHTML4: failed to render: 
java.util.MissingResourceException:
Can't find bundle for base name nls.CPResource, locale

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

This issue is documented under MetaLink BUG 8917620 & 8917611. The final disposition that is documented as:

Fixfox 3 does not work with e1 due to build id length

change in user agent string, and E1 fail to match it to

firefox pattern with shorter build date pattern.

The following is useragent string for

FF2: MOZILLA/5.0 (WINDOWS; U; WINDOWS NT 5.1; EN-US;

RV:1.8.1.17) GECKO/20080829 FIREFOX/2.0.0.17

FF3: MOZILLA/5.0 (WINDOWS; U; WINDOWS NT 5.2; EN-US;

RV:1.9.0.3) GECKO/2008092417 FIREFOX/3.0.3

Pattern in browsCap.ini for FF2

[*(Win*) Gecko/???????? Firefox/2.*]

Pattern in browsCap.ini for FF3

[*(Win*) Gecko/???????? Firefox/3.*]

With length of build id change from 8 digits to 10 digits

the matching does not work for firefox 3 and runtime fail

to render the E1 form. The solution is to change the match

patter to more generic format without length limitation of

build id by using single wildcard.

[*(Win*) Gecko/* Firefox/3.*]

The change shall be applied to all version of firefox start

from 3. And we may need to check the fix into 897, since

the customer may alread begin to use FF3 instead of FF2.

Author

Stewart Schatz

Career: Principal CNC Consultant for Syntax Systems Limited specializing Oracle JD Edwards EnterpriseOne and the technology that supports it. Side Hustle: Owner/Operator of E1Tips.com Location: Lancaster, PA USA  What I like to do: Invest in Family, Explore Technology, Lead Teams, Share Knowledge/Experience, Hunt, Hike, etc.
Happy
Happy
0
Sad
Sad
0
Excited
Excited
0
Sleepy
Sleepy
0
Angry
Angry
0
Surprise
Surprise
0

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Previous post The LINKBSFN Command Confusion
Next post Server Manager Timeout