ProcessConfigurationElement and IMemento
Hi,
Is there a uniform way to deal with IProcessConfigurationElement and IMemento? We implemented IOperationAdvisor (server side Precondition) and OperationDetailsAspectEditor (UI for configuring this precondition). We have to read and write the process configuration at the UI client side and also read it at the server side, so we wanted to share code. The problem is that OperationAdvisor.run accepts IProcessConfigurationElement and the OperationDetailsAspectEditor (saveState and restoreState) accepts IMemento. Our current thinking is to create ProcessConfigurationElementMemento. Thanks, Dekel |
2 answers
Jared Burns (4.5k●2●9)
| answered Oct 21 '08, 12:47 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi, Dekel.
There's really no uniform way. In our own code, I believe we just live with the duplication. Jared Burns Jazz Process Team dekelc wrote: Hi, |
Thanks.
We ended up with a partial implementation of IMemento called ProcessConfigurationElementMemento (implemented only 3-4 getters) which is good, at least for our needs. Dekel |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.