View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003859 | SymmetricDS Pro | Improvement | public | 2019-01-17 20:50 | 2019-05-08 17:29 |
| Reporter | pmarzullo | Assigned To | pmarzullo | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Target Version | 3.10.2 | Fixed in Version | 3.10.2 | ||
| Summary | 0003859: NodeService.findNode(...) (cached versus non-cached), where to use correct one | ||||
| Description | I looked at the calls to NodeService.findNode(...) (the non-cached versions, 40 of them) and summarized which ones can use the cached version. My logic was, if it had anything to do with changing the node, or registering the node, or reloading the node, it should call the non-cached version, otherwise use the cached version. Let me know what you think. symmetric-pro com.jumpmind.symmetric.console.ui.common.resolve.MissingTableResolver buttonClick(ClickEvent event) Should call (cached) findNode(String, boolean) com.jumpmind.symmetric.console.ui.screen.manage.ProcessInfoPanel refresh(ISymmetricEngine engine) Should call (cached) findNode(String, boolean) | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-01-17 20:50 | pmarzullo | New Issue | |
| 2019-01-17 20:50 | pmarzullo | Status | new => assigned |
| 2019-01-17 20:50 | pmarzullo | Assigned To | => pmarzullo |
| 2019-01-17 20:55 | pmarzullo | Status | assigned => resolved |
| 2019-01-17 20:55 | pmarzullo | Resolution | open => fixed |
| 2019-01-17 20:55 | pmarzullo | Fixed in Version | => 3.10.0 |
| 2019-01-17 20:55 | pmarzullo | Note Added: 0001383 | |
| 2019-05-08 12:37 | admin | Status | resolved => closed |
| 2019-05-08 17:29 | admin | Target Version | 3.10.0 => 3.10.2 |
| 2019-05-08 17:29 | admin | Fixed in Version | 3.10.0 => 3.10.2 |