Parent: #100

Is your feature request related to a problem? Please describe

Yes, for issue #100, support JDBC database operations.

Describe the solution you'd like

The generated analysis.json must be able to capture JDBC including operations using Connection, Statement, PreparedStatement, and ResultSet.

1. If the callsite ReceiverType is Statement, PreparedStatement, and CallableStatement

We want to look for the following methods:

2. CONNECTION and TRANSACTIONAL

3. ResultSet

4. CachedRowSet, FilteredRowSet, JdbcRowSet, JoinRowSet, RowSet, SyncResolver, WebRowSet

Describe alternatives you've considered

Same as #100

Additional context

• Use Daytrader8 to test.
• Other contexts are the same as Extend Codeanalyzer to Capture Database Entries #100
• May need to create new Entity classes and Enums for Transactions as below:

@Data
@NoArgsConstructor
@AllArgsConstructor
public class TransactionOperation {
    private int lineNumber = -1;
    private TransactionOperationType operationType;

    @NotImplemented
    private String savepointName;
    
    @NotImplemented
    private String transactionIsolationLevel;
    
    @NotImplemented
    private boolean autoCommitEnabled;
}

package com.ibm.cldk.javaee.utils.enums;

public enum TransactionOperationType {
    COMMIT,
    ROLLBACK,
    SAVEPOINT,
    SET_AUTOCOMMIT,
    SET_ISOLATION_LEVEL,
    ABORT,
    OTHER;
}

References

• https://cs.au.dk/~amoeller/papers/strings/strings.pdf