forked from Qortal/qortal
3d78d5dad9
qora.* packages are business logic/handler/processing data.* packages are "value objects" or are they "business objects"? toBytes(), fromBytes() (which used to be called parse()) and toJSON() moved to transform.* packages new issues: Lost control of SQL Transactions. Previously, some class "knew" whether to call COMMIT or not. e.g. simply saving a payment transaction would involve updating Transactions table first, then the PaymentTransactions table after (to satisfy foreign key constraints) then commit. Processing a block would involve a new transaction, a savepoint, a rollback and then maybe a further commit or rollback. Not sure how this is going to work with the repository, especially if business logic isn't supposed to be aware of such things. Growing number of stupid try-catch blocks. Probably best to ditch TransformationException (was ParseException) and throw IllegalStateExceptions instead as they're "unchecked". What happens if the repository fails to save() to the database? It can't throw SQLException any more as that has no meaning outside the repository. Ditto with delete(). |
||
|---|---|---|
| .. | ||
| blockchain.java | ||
| blocks.java | ||
| common.java | ||
| connections.java | ||
| crypto.java | ||
| exceptions.java | ||
| load.java | ||
| migrate.java | ||
| navigation.java | ||
| save.java | ||
| signatures.java | ||
| transactions.java | ||
| updates.java | ||