topic Adding aspects and lockiing nodes in one transaction in Alfresco Archive

Adding aspects and lockiing nodes in one transaction

akomisarek — Mon, 30 Nov 2009 08:27:57 GMT

Hello,I am having issues with following scenario which is performed in Dialog (I looked into BaseDialogBean code it seems my all action are wrapped into transaction which is something I would expect and shouldn't be worrying about that):1. If acted node is not multilingual made node multilingual.2.

Re: Adding aspects and lockiing nodes in one transaction

akomisarek — Mon, 30 Nov 2009 10:16:36 GMT

Hmm I am trying to fix it somehow but it seems I can't run anything in other transaction:

when I create RetryingTransactionHelper object in my bean expression helper.doInTransaction(callback, false, true); raises exception. txnService field in helper object is null and I get null pointer exception in alfresco's code:

                if (requiresNew)
                {
                    txn = txnService.getNonPropagatingUserTransaction(readOnly);
                }‍‍‍‍

I work on 3.2r version (built from 16803 revision).

Edit: added version and code. Changed sentence

Thanks in advance.

Re: Adding aspects and lockiing nodes in one transaction

akomisarek — Mon, 30 Nov 2009 10:42:22 GMT

Ignore my second post I found I should get transaction helper from repository rather than creating my own .

Last update from my side:

If I do my whole content in new transaction alfresco doesn't see my changes . So my documents aren't Multilingual / haven't aspects added / aren't locked. But execution completes without any error.

I am really lost right now cause I can't figure how to workaround this.. I really need to have all those actions performed on user intput.

Help would be greatly appreciated,
Adam

Re: Adding aspects and lockiing nodes in one transaction

lee — Wed, 21 Apr 2010 16:46:16 GMT

Hi Adam,

Did you ever find a solution to this?

I'm getting the same thing happening when behaviours fire on a node - though in my case it's custom behaviours that cause the problem (I can't see from the log attached whether the cause is a custom behaviour or a standard alfresco behaviour).

I'm assuming that the behaviour code needs to test whether a node is locked before attempting any changes to it (in your case createVersion).

But not really certain as that seems a bit arduous to add to all my behaviours.