Multi-layer XML customization

• US 8,560,938 B2
• Filed: 02/12/2008
• Issued: 10/15/2013
• Est. Priority Date: 02/12/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Barrow, Chris, Konduri, Gangadhar, Farrell, Ted, Triggs, Nicholas St. John
• Primary Examiner(s): Mills, Frank D
• Application Number:
  US12/029,600
• Publication Number:
  US 20090204884A1
• Time in Patent Office: 2,072 Days
• Field of Search: 715/235, 715/234
• US Class Current: 715/234
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Embodiments of the present invention provide techniques for customizing aspects of a metadata-driven software application. In particular, embodiments of the present invention provide (1) a self-contained metadata engine for generating customized metadata documents from base metadata documents and customizations; (2) a customization syntax for defining customizations; (3) a customization creation/update component for creating and updating customizations; (4) a customization restriction mechanism for restricting the creation of new customizations by specific users or groups of users; and (5) memory and caching optimizations for optimizing the storage and lookup of customized metadata documents.

Claims

1. A method for customizing a software application, the method comprising:

receiving, by a computer system, a base metadata document defining one or more characteristics of at least a portion of the software application;

identifying, by the computer system, a plurality of customization documents defining modifications to the base metadata document, wherein the plurality of customization documents are stored separately from the base metadata document, and wherein the identifying the plurality of customization documents comprises;

determining a plurality of customization levels associated with the base metadata document, each of the plurality of customization levels representing a scope for which the base metadata document can be customized, the plurality of customization levels being determined by accessing a configuration file comprising mappings between customization levels and base metadata documents, wherein the plurality of customization levels are sorted in a precedence order; and

identifying a customization document for each customization level in the plurality of customization levels, wherein the customization document is identified based on one or more runtime attributes corresponding to the customization level; and

generating, by the computer system, a customized metadata document by applying the plurality of customization documents to the base metadata document in the precedence order.

2. The method of claim 1, wherein the steps of receiving, identifying, and generating are performed at runtime of the software application.

3. The method of claim 1, further comprising using the customized metadata document to generate a user interface of the software application.

4. The method of claim 1, wherein the base metadata document, the plurality of customization documents, and the customized metadata document are Extensible Markup Language (XML) documents.

5. The method of claim 1, wherein the steps of receiving, identifying, and generating are performed by a metadata engine configured to provide application metadata to one or more components of the software application.

6. The method of claim 5, wherein the metadata engine is capable of interoperating with any software application that makes use of XML-based application metadata.

7. The method of claim 1, wherein the plurality of customization documents are stored in a predefined location relative to the base metadata document.

8. The method of claim 1, wherein the plurality of customization documents and the base metadata document are stored in separate storage repositories.

9. The method of claim 1, wherein the plurality of customization levels are configurable.

10. The method of claim 1, wherein the plurality of customization documents are applied cumulatively.

11. The method of claim 1, wherein the plurality of customization levels associated with the base metadata document are stored in an XML-based configuration file.

12. The method of claim 1, wherein the plurality of customization documents include at least one seeded customization document provided by a supplier of the software application.

13. The method of claim 1, wherein the plurality of customization documents include at least one user customization document created by a user of the software application.

14. The method of claim 1, wherein the software application may be upgraded without modifying the plurality of customization documents.

15. The method of claim 1, wherein the one or more characteristics include content, behavior, or appearance.

16. A system for customizing a software application, the system comprising:

a repository configured to store a base metadata document and a plurality of customization documents, wherein the base metadata document defines one or more characteristics of at least a portion of the software application, wherein the plurality of customization documents define modifications to the base metadata document, and wherein the plurality of customization documents are stored separately from the base metadata document; and

a processor configured to;

receive the base metadata document;

identify the plurality of customization documents by;

determining a plurality of customization levels associated with the base metadata document, each of the plurality of customization levels representing a scope for which the base metadata document can be customized, the plurality of customization levels being determined by accessing a configuration file comprising mappings between customization levels and base metadata documents, wherein the plurality of customization levels are sorted in a precedence order; and

identifying a customization document for each customization level in the plurality of customization levels, wherein the customization document is identified based on one or more runtime attributes corresponding to the customization level; and

generate a customized metadata document by applying the plurality of customization documents to the base metadata document in the precedence order.

17. The system of claim 16, wherein the processor is configured to perform the steps of receiving, identifying, and generating at runtime of the software application.

20. The system of claim 16, wherein the processor is configured to use the customized metadata document to generate a user interface of the software application.

18. A non-transitory machine-readable medium for a computer system, the non-transitory machine-readable medium having stored thereon a series of instructions which, when executed by a processing component, cause the processing component to customize a software application by:

receiving a base metadata document defining one or more characteristics of at least a portion of the software application;

identifying a plurality of customization documents defining modifications to the base metadata document, wherein the plurality of customization documents are stored separately from the base metadata document, and wherein the identifying the plurality of customization documents comprises;

determining a plurality of customization levels associated with the base metadata document, each of the plurality of customization levels representing a scope for which the base metadata document can be customized, the plurality of customization levels being determined by accessing a configuration file comprising mappings between customization levels and base metadata documents, wherein the plurality of customization levels are sorted in a precedence order; and

identifying a customization document for each customization level in the plurality of customization levels, wherein the customization document is identified based on one or more runtime attributes corresponding to the customization level; and

generating a customized metadata document by applying the plurality of customization documents to the base metadata document in the precedence order.

19. The non-transitory machine-readable medium of claim 18, wherein the steps of receiving, identifying, and generating are performed at runtime of the software application.