topic Re: Change made through a webscript not reflected on ShareUI in Alfresco Archive

Change made through a webscript not reflected on ShareUI

annakan — Thu, 14 Apr 2011 17:46:09 GMT

Hello all,I am trying to make changes to nodes through a webscript not although all API call are ok (not raising any error), NOTHING is translated in the shareUI.The exact same thing happens when I run code into the debugger evaluate console Taking a leaf from http://wiki.alfresco.com/wiki/JavaScrip

Re: Change made through a webscript not reflected on ShareUI

annakan — Thu, 14 Apr 2011 19:40:40 GMT

First things I was missing :

change in the debugger do not reflect in the repository, probably different transaction or thread+transactions

Second thing I was missing :

TargetFolder.addNode(actionedUponNodeRef)

SourceFolder.removeNode(actionedUponNodeRef)

no need to fidle with the relationships.

I really need to wrap my head better around the alfresco content model beyond the "everything is a node" simple thing.
The java and javascript API differs a bit too, in java you do nodeService.addChild(ParentNode, actionedUponNodeRef, AssocType, AssocQname), I suppose javascript does not support directly adding "typed" containment relationships.

Everything works but I still have a bug when I added a node to a folder, added it multiple parents, and then suppress the node, the folder it was added first seems to Keep a hidden reference to it that prevent adding it again. (many retries then ibatis sql error

Caused by: com.ibatis.common.jdbc.exception.NestedSQLException:
— The error occurred in alfresco/ibatis/#resource.dialect#/node-insert-SqlMap.xml.
— The error occurred while applying a parameter map.
— Check the alfresco.node.insert_ChildAssoc-InlineParameterMap.
— Check the statement (update failed).
— Cause: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '4958-33-2164579964-c4_small.jpg' for key 'parent_node_id'
        at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeUpdate(MappedStatement.java:107)
        at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.insert(SqlMapExecutorDelegate.java:393)
        at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.insert(SqlMapSessionImpl.java:82)
        at org.springframework.orm.ibatis.SqlMapClientTemplate$8.doInSqlMapClient(SqlMapClientTemplate.java:366)
        at org.springframework.orm.ibatis.SqlMapClientTemplate.execute(SqlMapClientTemplate.java:200)
        … 129 more‍‍‍‍‍‍‍‍‍‍‍‍

I don't know if it is an alfresco bug for being "on the fringe" with multiple parents, or something I induce by mis-using the API.

Neither do I know if I should do some clean-up in the onBeforeDelete behavior ?

Re: Change made through a webscript not reflected on ShareUI

mrogers — Fri, 15 Apr 2011 08:03:10 GMT

Glad you got beyond last night's problems.

You are posting long posts containing many different issues which makes it difficult to respond.
Perhaps you could start by saying what are you trying to do? Rather than jumping to implementation.

Re: Change made through a webscript not reflected on ShareUI

annakan — Tue, 19 Apr 2011 14:41:49 GMT

Thanks for your reply.

Though everything is explained inline with references to my previous posts explaining both the problem and the context, I did not want to reproduce them and clutter even more the post or cross post.

Basically my post boils down to this :

First part is about the debugger obviously not allowing to experiment with the API because wathever call or change I make in it does not reflect on the repository I can browse through the web. Probably a transaction or session thing.
Could this be confirmed as a fact ?

The second part is about the fact that this experience lead me to doubt about what I was experiencing while trying to build my webscript based action.
I was trying to add and remove parents from a node to no avail, and my experiences in the debugger were, to say the least inconclusive too, leading me to think that the API might be "faulty" in the way I used it.
Later on I discovered there was a higher level API to add and remove parents with TargetFolder.addNode(actionedUponNodeRef) & SourceFolder.removeNode(actionedUponNodeRef)
that wraps the nodeService.addChild(ParentNode, actionedUponNodeRef, AssocType, AssocQname) with a "contains" kind of relationship.
It still does not explain why I could not do it "directly" through the nodeRef.parents property but I suspect the javascript wrapping does so many magic behind the scene that sometimes it get itself lost. At the very least the semantic is unclear, at least to me.

My last problem was when deleting a node some leftover datas were preventing me to add the same document again, I add to implement the beforeDelete behavior with the "NotificationFrequency.FIRST_EVENT" policy to be able to remove the non primary parents from the node before deletion.

Why all this : because I want to properly support multiple parents for nodes, so that a document can really appears in multiple folders at once. I must say I constantly discovers new creative ways the "primary parent = container" is entrenched into the shareUI (for instance the "path webscript" that is used when constructing the crumb on a document detail page …. ), it is like the concept of "context" (where I came from as a user, where I am sited on as a document) is for now absent from share. Most assumption seems to be that the document is "self describing" in full, and that is not right neither in practice nor in the underlying model (where multiple parents ARE supported for the best).

I hope it answered your questions, I already have more to ask…