Kavin's SOA Blog

May 11, 2009

Rule Author compatibility with Browsers

Rule Author does not work with Firefox 3, IE8, IE8 (Compatibility View), Chrome browser. It seems like issue is with Oracle UIX framework (which rule author uses extensively), which provides AJAX-style functionality. UIX was developed before these browsers were released, and unfortunately we face these incompatibilities. There are several issues with the partial page rendering and the popup windows do not work, preventing the user from editing rules.

So if you are getting similar kind of errors, before trying to validate your install, please check your browser. My savior was Safari with disabled pop-up blocker. IE8 and my dependable browser Firefox ditched me. Their “browser” button didn’t returned correct values resulting in these errors.

  • Cannot perform operation. ‘RUL-01213: Error initializing the repository. Please refer to the base exception. Root Cause: ‘C:\fakepath\testRepository’ does not exist.
  • Cannot perform operation. ‘RUL-01029: XML Schema C:\fakepath\fault.xsd does not exist. ‘
  • Cannot perform operation. ‘RUL-01029: XML Schema fault.xsd does not exist. ‘

April 16, 2009

Understanding Oracle Application Server Release Number

Filed under: Information — Tags: , — Kavin @ 11:34 pm

To understand the release level nomenclature used by Oracle, examine the example of an Oracle Application Server release number shown

Example of an Oracle Release Number

  • Major Oracle platform number

    This is the most general identifier. It represents a major new edition (or version) of an application, such as Oracle database server or Oracle Application Server, and indicates that the release contains significant new functionality.

  • Database maintenance release number

    This digit represents a maintenance release level. Some new features may also be included.

  • Application Server release number

    This digit reflects the release level of Oracle Application Server.

  • Component-specific release number

    This digit identifies a release level specific to a component. Different components can have different numbers in this position depending upon, for example, component patch sets or interim releases.

  • Platform-specific release number

    This digit identifies a platform-specific release.

Create a free website or blog at WordPress.com.