#1316 closed defect (rejected)
Caching of operators can cause dependency problems
| Reported by: | epitzer | Owned by: | epitzer |
|---|---|---|---|
| Priority: | medium | Milestone: | |
| Component: | General | Version: | 3.3.2 |
| Keywords: | Cc: |
Description
Many Problem classes have a list of operators that are suitable for a particular problem and have been parameterized accordingly. However, as these operators are dynamically discovered, references to arbitrary assemblies can be made. If a problem is persisted and later restored with some of these assemblies missing the file cannot be loaded even though no operators of this assembly are used anywhere in the problem or algorithm.
Change History (4)
comment:1 Changed 14 years ago by swagner
- Owner changed from swagner to abeham
- Status changed from new to assigned
comment:2 Changed 14 years ago by abeham
- Milestone changed from HeuristicLab 3.3.3 to HeuristicLab x.x.x
- Owner changed from abeham to epitzer
comment:3 Changed 14 years ago by epitzer
- Resolution set to rejected
- Status changed from assigned to closed
comment:4 Changed 14 years ago by swagner
- Milestone HeuristicLab x.x.x deleted
Note: See
TracTickets for help on using
tickets.
After discussion with abeham this issue is deemed to complicated to implement: Operators need to be cached so they can be customized after the algorithm has requested them and changes to the problem have been made. If no references are stored these links are lost and operators can no longer be customized. However, the Problem class has no way of knowing which operators are used within the algorithm.
Moreover, as this issue will not occur in pristine release builds without additional plug-ins, we won't fix it for now.