topic Re: Transactions and Repository Actions in Alfresco Archive

Transactions and Repository Actions

pjaromin — Mon, 17 Sep 2012 13:33:08 GMT

I have an external process that renders repository content based on node properties. This is facilitated by a repository Action that calls on this external application. The external application in turn makes calls back to the repository to gather key bits of information used in the rendering process

Re: Transactions and Repository Actions

mrogers — Mon, 17 Sep 2012 14:20:35 GMT

Could you gather your information prior to creating the new node?

The alternative is to trigger your external actions "post commit" so its called after node creation.

Or you could have some sort of queue of nodes to be processed?

Re: Transactions and Repository Actions

pjaromin — Mon, 17 Sep 2012 15:02:14 GMT

Thanks for the response.

The alternative is to trigger your external actions "post commit" so its called after node creation.

Yeah, that's what I'm trying to do, but I don't know exactly how/where I can do this. The aspect (behavior) is already set to

new JavaBehaviour(this, "onAddAspect", NotificationFrequency.TRANSACTION_COMMIT)‍

.

I tried calling my own variation of the "CopyAction" that put the result in PARAM_RESULT within my main action. And then triggering the render. However the new node still isn't accessible until after the primary/calling action completes.

I'm assuming this is a transactional thing, perhaps it's more/different than that?

Or you could have some sort of queue of nodes to be processed?

Does such a queue exist that I could hook into?

Here's a quick/crude drawing to illustrate the sequence:

[img]https://dl.dropbox.com/u/35767566/alfresco-render-action.png[/img]

Re: Transactions and Repository Actions

mrogers — Mon, 17 Sep 2012 16:04:28 GMT

Yes - that looks very much like the Alfresco Transformation Server.

Re: Transactions and Repository Actions

pjaromin — Mon, 17 Sep 2012 21:39:39 GMT

Does the architecture for that system create a note and kick off external rendering within the same action?

What's done to make the newly-minted node accessible externally before the action returns?

-Patrick

Re: Transactions and Repository Actions

pjaromin — Wed, 19 Sep 2012 14:51:22 GMT

I wound up putting the rendering process in a separate action that I execute asynchronously from within the main action.

This has worked so far, however I'm guessing I've set up a race condition where it's conceivable that the asynchronous action may for some reason execute before the main thread commits, no?

I really want this new rendition to replace the cm:content of the newly-minted node. Another alternative I suppose would be to trigger the re-render upon the first "download" request by modifying or replacing the default "Download" action for this custom node type.

Any other ideas?