Dynamic java bean for visualage for java

• US 9,298,481 B2
• Filed: 08/29/2014
• Issued: 03/29/2016
• Est. Priority Date: 07/14/2000
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wason, James R.
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US14/473,055
• Publication Number:
  US 20140372964A1
• Time in Patent Office: 578 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 8/33 Intelligent editors
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A uniform strategy for the general problem of providing custom editors and initialization strings for beans (all “dynabeans” inherit from a common bean class that incorporates this strategy. This is then extended to allow the initialization strings to be stored in a relational database. The database function is an extension of the function provided by the VisualAge Persistence Builder (using some of the EADP extensions). An important advantage of this approach is that many changes to the application can now be handled by adjusting the database version of the bean definition, without a need to touch the underlying code. This will reduce down time for the application, and also improve application stability.

Claims

1. A method of managing application definitions used in a computer application, comprising:

storing initialization strings for the application definitions in a database, each of the application definitions using associated values, and each of the initialization strings including a value for an associated application definition;

using a custom editor, separate from the computer application, to access the initialization strings in the database to use the initialization strings to initialize the application definitions;

the computer application accessing the initialization strings, via the custom editor, to pass the values of the initialization strings to the application definitions for use by the application definitions; and

providing an administrator with access to the initialization strings, independent of the computer application, via the custom editor, to change one or more of the values of the application strings, whereby the values used by the application definitions are changed without changing the computer application; and

wherein;

the storing the initialization strings in the relational database includes

using a storage method for storing the initialization strings, including, for each of the application definitions, passing to the storage method one of the initialization strings, an encloser, the value and a new value for said each application definition, the storage method finding and deleting all matching rows in the relational database, breaking the passed one of the initialization strings into a plurality of segments, and adding a new row in the relational database for said each segment; and

the method comprises the further step of using the custom editor for the storing the initialization strings in the relational database, and using the same custom editor to alter, change, add and delete the application definitions in the relational database while running the computer application.