It's all about the answers!

Ask a question

ProcessConfigurationElement and IMemento


Dekel Cohen (14681) | asked Oct 19 '08, 10:15 a.m.
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



permanent link
Jared Burns (4.5k29) | 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,
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

permanent link
Dekel Cohen (14681) | answered Oct 23 '08, 5:08 a.m.
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


Register or to post your answer.