all bits considered data to information to knowledge

28Apr/110

Inconsistent behavior in Oracle 10g XE Web Interface

Oracle 10g Express edition comes with a nice web interface to it - APEX - Oracle Application Express which is a  rapid development tool for Web applications on the Oracle database.

While using the tool for my Discovering SQL book, I have noticed some inconsistent behavior which I attribute to DHTML implementation in this particular version (10g Express).They appear to be OS dependent since I have not encountered these in either Windows XP or Windows Vista installations.

 

The inconsistencies of the browser behavior can be grouped into two major categories - local and remote.

Accessing Oracle 10g XE with APEX on local machine (e.g. http://127.0.0.1:8080/apex/)

The Opera(v. 11.10)  browser along with Chrome (v. 10.0.648.205) and Firefox (v.  4.0) running on Windows 2003 Server - all cannot display uploaded scripts as shown on the pictures below. This behavior is not dependent on length of the script or on script file encoding (UTF-8, code pages etc). I supply exact versions used, but this will hold true for the earlier versions as well. The only browser that correctly displayed the script on local machine was Internet Explorer  (v. 8.0.6001.18702),

The gallery: Chrome, Firefox, IE, Opera; then remote IE, Opera and Firefox, respectively.

Accessing Oracle 10g XE with APEX on remote machine (e.g. http://remotemachine.net:8080/apex/)

All the browsers break when a source of the script is accessed through Apex interface remotely (only Internet Explorer gives a meaningful error). The fifth picture in the above gallery shows Oracle PL/SQL error along with DHTML tags.

4May/100

.Net as Will and Representation

It's been a long run for .Net in the wild... The experiment with letting go is about to end, and .Net is to become yet another Windows "component".

The update to .NET Framework policy states that beginning with .NET Framework 3.5 Service Pack 1 (SP1) the .NET Framework will be defined as a “Component”. As a Component, .NET version 3.5 Service Pack 1 (SP1) will assume the same Support Lifecycle policy as its parent product or platform.

As Yogi Berra might have remarked: "It's déjà vu all over again!"  Yes, I am referring to Internet Explorer 4.0 being "integral part of Microsoft Windows".
I think this is a major blunder on Microsoft's part, and an opening for Java to regain some of the lost ground (the last time I've checked JVM was still a separate product...)

Tagged as: , , , No Comments