Hide Forgot
Description of problem: when clients creating VM from template they performing several steps: 1. get VmTemplate 2. create VmStatic class (that will be passed to BE later) 3. copy content of VmTemplate to VmStatic class (on property level) 4. override VmStatic class content with content specified by user 5. pass VmStatic class to BE RFE: both VmStatic and VmTemplate inherits from VmBase, please move VmStatic properties to VmBase and re-use them at VmTemplate, (currently the doubled) this way steps 1 - 3 won't be required and any new feature that will be added to VmTemplate will be automatically exposed to clients
1. that's not a code change i see happening for 3.0 (unless trivial) 2. not sure how aligns with DAO's layout. 3. can also be solved with a helper method/command.
1. helper method - not good for serialization 2. command - is much more complicated than simple polymorphism
how does helper method not good for serialization, but polymorphism is?
- 'polymorphism' supported at serialization, (eg. VmTemplate::VmBase will be preserved after class serialized so BE can require in parameters class VmBase instead of VmStatic) - 'methods' are not serialized
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.