topic Re: Upload new Version calls onUpdateNode twice with bogus NodeRef in Alfresco Archive

Upload new Version calls onUpdateNode twice with bogus NodeRef

technaton — Fri, 05 Dec 2014 10:53:52 GMT

Hello everybody,I've created a behavior along with a custom aspect that implements the OnUpdateNodePolicy‍ interface. The behavior itself does nothing spectacular: It creates or updates a PDF using the content transformation service.Now, when uploading a new version of the document that already has

Re: Upload new Version calls onUpdateNode twice with bogus NodeRef

afaust — Fri, 05 Dec 2014 14:09:23 GMT

Hello,

uploading a new version via Share is actually done using a temporary working copy. This working copy is probably your non-existent node because I presume your behaviour is bound to TRANSACTION_COMMIT and the working copy has already been deleted again at that point. For TRANSACTION_COMMIT behaviours you always HAVE TO include existence and other checks (e.g. does the trigger condition still apply?) because anything could have happend between the behaviour being schedule and actually being executed.

Regards
Axel

Re: Upload new Version calls onUpdateNode twice with bogus NodeRef

technaton — Fri, 05 Dec 2014 14:54:00 GMT

Hello Axel,

thank you very much for the explanation. You are right, the behavior is tied to

TRANSACTION_COMMIT‍

.

Regards
Eric