Timeline for Refactoring instanceOf, moving logic to POJO when it has database interaction
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2023 at 15:14 | vote | accept | Accollativo | ||
| Jan 20, 2023 at 15:02 | history | edited | Aiono | CC BY-SA 4.0 |
added 400 characters in body
|
| Jan 20, 2023 at 14:59 | comment | added | Aiono | The visitor interface should reside in the POJO project, then there is no circular dependency. It already should because "Visitor" is not a business logic. It's just a way to process your POJO. Visitor implementations are business logic. | |
| Jan 20, 2023 at 14:35 | comment | added | Accollativo | I thought a solution with this same problem. The business logic (where is instanceOf) and pojo (RecordA) are in 2 separate project, and this would mean to include in the pojo app, the maven dependency to the business project (the Visitor in this case), and this don't look good to me. Maybe it can generate a circular dependency. Or maybe if I keep the Visitor interface in the POJO project, and the Visitor implementation in the business project, your solution can work. | |
| Jan 20, 2023 at 13:42 | history | answered | Aiono | CC BY-SA 4.0 |