Java OO Methodology for applications which must support multiple vendors
Original Publication Date: 2004-Sep-20
Included in the Prior Art Database: 2004-Sep-20
This invention is a Methodology which involves abstracting common attributes from multiple vendors/languages (database table creation, SQL), and using sound OO Design principles to harvest those commonalities and minimize differences when programming. The methodology involves using a java class to pull together the commonalities and using java subclasses to handle any different vendor dialects. Below is an example of this Methodology, applicable to different database vendors and database table creation. Typically, Database Table definitions are stored in executable database scripts. These scripts are executed and the database tables are created. If an IBM product needed to support multiple database vendors, then a separate table creation script would be required for each database vendor. This violates sound OO Design principles. For example, if a Table name needed to be changed, the change would need to be made in each script, instead of in one central location. This is extremely problematic and could lead to unforeseen errors. The change could be made in one vendor's script but not in another, typos could occur when editing multiple scripts etc....