Configuration file processing

• US 20040194053A1
• Filed: 12/10/2003
• Published: 09/30/2004
• Est. Priority Date: 06/27/2001
• Status: Abandoned Application

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Bonsma, Erwin R
• Application Number:
  US10/480,142
• Publication Number:
  US 20040194053A1
• Time in Patent Office: Days
• US Class Current: 717/100
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Software object class (9, 10, 13, 14) are provided with methods for roles within a program and methods for processing of a configuration file (6) for the program Accordingly, a first program and second program, which is a configuration utility for the first program, are constructed using the classes so that configuration data can be validated within the first program and during

Claims

1. A software system comprising:

a first program;

a second program; and

a configuration data store storing configuration data for the first program, the second program being a configuration tool for editing said configuration data,

wherein the first and second programs are constructed using a common class, said common class comprising a method for validating configuration data for the first program and a method for providing information regarding the type and/or the valid values for said configuration data for the first program.

2. A software system according to claim 1, wherein the first program is configured to:

create an instance of said common class, said instance being loaded with configuration data from said configuration data store and validating said data;

create an instance of a further class; and

initialise the instance of said further class using the configuration data loaded into said instance of said common class.

3. A software system according to claim 2, wherein the first program is configured to:

create a further instance of said further class; and

initialise the further instance of said further class using the loaded configuration data loaded into said instance of said common class.

4. A software system according to claim 2 or 3, wherein the first program is configured to:

create a further instance of said common class, said instance being loaded with a respective set of configuration data from said configuration data store and validating said data;

create a further instance of said further class; and

initialise said further instance of said further class using the configuration data loaded into said further instance of said common class.

5. A software system according to any preceding claim, including a further common class, wherein the first program and the second program are configured to create respective independent prototype instances of said common classes and the first program is configured to clone an instance of said common class, said cloning including instantiating an instance of the further common class as a member of the cloned instance of said common class.