Automated transaction and datasource configuration source code review

A computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store, the method comprising the steps of, wherein each step is performed by a processor of a computer:

• receiving a request to review configuration source code files seeking to access the data store;
• checking, using the processor of the computer, the configuration source code files for a definition of a transaction manager, wherein the definition includes a bean;
• setting an issue flag if the configuration source code files do not include the definition of the transaction manager;
• checking, using the processor of the computer, the configuration source code files to determine whether a transaction definition is at an outer boundary of a service object or a method;
• setting the issue flag if the transaction definition does not appear before the start of the service object class or method definition;
• checking, using the processor of the computer, the configuration source code files for loops within a service object method definition;
• setting the issue flag if service object method definition includes any loop structures;
• checking, using the processor of the computer, the configuration source code files for exception handling within data access object method definitions that change the contents of the data store, wherein the exception handling within data access object method definitions includes the term “throws” followed by a name of an exception handler cited in the first line of the method definition;
• setting the issue flag if the method definition does not include an exception handler;
• checking, using the processor of the computer, the configuration source code files for changes in isolation level;
• setting the issue flag if the configuration source code files include the term “read committed” or “read uncommitted”;
• checking, using the processor of the computer, the configuration source code files for a datasource definition;
• setting the issue flag if the datasource definition is not present or does not include a predetermined address;
• reviewing the status of the issue flag;
• issuing a halt signal if the issue flag is set;
• and
• issuing a proceed signal if the issue flag is not set.

A computer-implemented automated review method for transaction and datasource configuration source code files seeking to access a data store, the method comprising the steps of, wherein each step is performed by a processor of a computer:

• receiving a request to review configuration source code files seeking to access the data store;
• checking, using the processor of the computer, the configuration source code files for a definition of a transaction manager, including an address of a database connectivity framework transaction manager;
• setting an issue flag if the configuration source code files do not include the definition of the transaction manager or the address is incorrect;
• checking, using the processor of the computer, the configuration source code files to determine whether a transaction definition is at an outer boundary of a service object or a method;
• setting the issue flag if the transaction definition does not appear before the start of the service object class or method definition;
• checking, using the processor of the computer, the configuration source code files for loops within a service object method definition;
• setting the issue flag if service object method definition includes any loop structures;
• checking, using the processor of the computer, the configuration source code files for exception handling within data access object method definitions that change the contents of the data store, the exception handling including the term “throws” followed by a name of an exception handler cited in the first line of the method definition;
• setting the issue flag if the method definition does not include the exception handler;
• checking, using the processor of the computer, the configuration source code files for changes in isolation level;
• setting the issue flag if the configuration source code files include the term “read committed” or “read uncommitted”;
• checking, using the processor of the computer, the configuration source code files for a datasource definition;
• setting the issue flag if the datasource definition is not present or does not include a predetermined address;
• reviewing the status of the issue flag;
• issuing a halt signal if the issue flag is set;
• and
• issuing a proceed signal if the issue flag is not set.