do you mean that you are gonna catch that exception and according to activation status just log it?
Yep
If this is not the case, please just ignore the following comments.

If this is the case, unfortunately I cannot agree that this is a real fix. I real fix imo should take care not to reach the exception. I think we need some more work on this item.

First: we need a running system which works with the same semantic as it worked in later versions then we can find nice solutions for a future one.

I hope you and Sameer will solve the problem from bottom up during implementing the new activation mechanism. Here some words about the problem.

- there is no real referencing from on system to the other, since only the path of a node is used - if an activated note moves (renaming is a sort of moving) he looses the relation to the node in the public instance (we deactivate it because else the user would need to delete the node manually in the subscribed instance) - there is no guarantee that the activated flag has the right state. perhaps the public instance was changed (no feedback, no update). - an instance can have more than one subscriber: to which does the activation flag relate?

The method to solve this in the current 2.1 version:
- try always to deactivate (independent of what the flag is saying)
- if the deactivation false because the node was missed on the public side and the current state says that this node was NOT activated: ignore the error since this is ok - if the deactivation false because the node was missed on the public side and the current state says that this node should be activated: write a log message.

A real solution will take more time than we have to fix 2.1.2.

If you like, open a new JIRA Task for this problem. Perhaps we can keep all the activation issues together in one main task.

Philipp Bracher

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to