Hi Anya!Some weeks ago i had the same problem. I made some tests and sourcecode research and found out the following behaviour:- there are 2 different meanings of the name - the cm:name property and the child-assoc QName (don't misswatch with assoc type qname!)
- only the Alfresco Web-Client manages to rename both in synch (renaming files/folders)
- note, the nobody else in the system helps you keeping the 2 names in synch (in my opinion this is a conceptual problem)
:idea: So i implemented a behaviour which helps:
public class NameQNameSynchBehaviour implements OnUpdatePropertiesPolicy, OnMoveNodePolicy {
/** a class specific logger */
private Logger logger = Logger.getLogger(NameQNameSynchBehaviour.class);
PocService pocService;
public void onUpdateProperties(
NodeRef nodeRef,
Map<QName, Serializable> before,
Map<QName, Serializable> after) {
logger.debug("onUpdateProperties: " + nodeRef);
// name changes
String nameBefore = before.get(ContentModel.PROP_NAME);
String nameAfter = after.get(ContentModel.PROP_NAME);
boolean nameChanged = (nameBefore != null && nameBefore != nameAfter)
if (nameChanged==true) {
logger.debug("Poc name has changed – nameBefore: $nameBefore, nameAfter: $nameAfter");
ChildAssociationRef newChildRef = pocService.changePrimaryParent2ChildAssocQName(nodeRef, nameAfter);
logger.debug("Poc qname has been synched: ${newChildRef.getQName()}");
}
}
/*
* (non-Javadoc)
*
* @see
* org.alfresco.repo.node.NodeServicePolicies.OnDeleteNodePolicy#onDeleteNode
* (org.alfresco.service.cmr.repository.ChildAssociationRef, boolean)
*/
public void onMoveNode(ChildAssociationRef oldChildAssocRef, ChildAssociationRef newChildAssocRef) {
logger.debug("onMoveNode - OLD: " + oldChildAssocRef + " - NEW: " + newChildAssocRef);
// track qname changes (we can't do any more here)
QName qnameBefore = oldChildAssocRef.getQName();
QName qnameAfter = newChildAssocRef.getQName();
boolean qnameChanged = (!qnameBefore.equals(qnameAfter));
if (qnameChanged==true) {
logger.debug("Poc qname has changed – qnameBefore: $qnameBefore, qnameAfter: $qnameAfter");
// FIXME we can't backward-synch the cm:name, cause the qname may be a cutted version of a longer name
}
}
}
public class PocService {
NodeService nodeService;
public QName createNewChildAssocQName(ChildAssociationRef childAssoc, String newNameWithExt) {
String localName = QName.createValidLocalName(newNameWithExt); // name will be croped to a maximum of 100 chars
return QName.createQName(childAssoc.getQName().getNamespaceURI(), localName);
}
public ChildAssociationRef changePrimaryParent2ChildAssocQName(NodeRef node, String newNameWithExt) {
return changeChildAssocQName(nodeService.getPrimaryParent(node), newNameWithExt);
}
public ChildAssociationRef changeChildAssocQName(ChildAssociationRef childAssoc, String newNameWithExt) {
QName newAssocQName = createNewChildAssocQName(childAssoc, newNameWithExt);
if (newAssocQName.equals(childAssoc.getQName())) {
return childAssoc; // qname has not changed!
}
return nodeService.moveNode(
childAssoc.getChildRef(), childAssoc.getParentRef(),
childAssoc.getTypeQName(), newAssocQName);
}
}
But there are some problems around this:- current user needs the permission "createChildren" to change the child assoc
- the QName will be cutted to a maximum length of 100 chars, so the names may even differ!
:cry: problems like this make alfresco development a very hard job! :cry:
