topic Re: Problem with getChildByName in Alfresco Archive

Problem with getChildByName

dwighth — Fri, 10 Aug 2007 16:39:22 GMT

Hi.I always get a null from NodeService.getChildByName() and FileFolderService.resolveNamePath(). Since FileFolderService.resolveNamePath() uses NodeService.getChildByName(), I suspect the problem is with the latter.I'm trying to get Company Home as my test, but to no avail. I've tried every combin

Re: Problem with getChildByName

derek — Thu, 16 Aug 2007 10:02:21 GMT

Hi,

There are other methods to match the association QName, which is app:company_home. You need to look for the actual name, which will be Company Home. The FileFolderService completely hides the use of associations and works only with the display names as stored in property cm:name.

Regards

Re: Problem with getChildByName

dwighth — Thu, 16 Aug 2007 16:11:35 GMT

Hi.
Thanks for the response.

The use of common name by the FileFolder methods is what I had understood from the javaDocs as well. However, that doesn't seem to get around my problem. When I try the following calls


fileFolderService.listFolders(root);
fileFolderService.search(root, "Company Home", false);
‍‍‍‍

I get a List containing the Company Home node. That's what I'd expect. However, when I call


fileFolderService.searchSimple(root, "Company Home");
‍‍‍

I get null.

When I do


List<String> nodePath = new ArrayList<String>();
nodePath.add("Company Home");
fileFolderService.resolveNamePath(root, nodePath);
‍‍‍‍‍

I get a FileNotFound exception. I've tried it with a preceding slash and get the same result.

Any insight that you can give me is appreciated.

Thanks;
Dwight

Re: Problem with getChildByName

derek — Fri, 17 Aug 2007 05:26:20 GMT

Hi,
FileFolderService originally threw out any operations that weren't performed against the cm:content-cm:folder model. That constraint was relaxed a little over time. It remains, however, a model-specific service.

Company Home is the top-level cm:folder in the hierarchy. You're expected to know what its NodeRef is. The root node is not a cm:folder and FileFolderService should really have nothing to do with it. The type of association between the root node and the Company Home node is not the type that FileFolderService serves.

That being said, the search code should also return no results in order to be consistent - but it's a minor issue.
Think of Company Home as being the root of the file-folder hierarchy. You need it before you can use FileFolderService. To get it, make a quick call to the NodeService

QName qname = QName.createQName(NamespaceService.APP_MODEL_1_0_URI, "company_home");
List<ChildAssociationRef> assocRefs = nodeService.getChildAssocs(rootNodeRef, ContentModel.ASSOC_CHILDREN, qname);‍‍

From that point on, you're in the hierarchy with the model that the FileFolderService uses.

Regards

Re: Problem with getChildByName

derek — Fri, 17 Aug 2007 05:29:32 GMT

Another thing: If you're concerned about having to know the company home association QName out of the blue, it is available as an injectable property spaces.company_home.childname. This is how our services get hold of it.

Re: Problem with getChildByName

dwighth — Fri, 17 Aug 2007 15:09:00 GMT

Hi.
Great - thanks, that explains it.

Appreciate the time & effort…

Regards;
Dwight

Re: Problem with getChildByName

derek — Mon, 20 Aug 2007 10:02:59 GMT

You're welcome. Good luck.

Re: Problem with getChildByName

kdejaeger — Wed, 18 Jun 2008 14:00:58 GMT

Hello,

I wrote some code using the filefolderservice and stumbled upon a similar problem.
You can see the code sniplet in this post http://forums.alfresco.com/en/viewtopic.php?f=4&t=12891 .

The arguments given to the function resolveNamePath are easy:
* first argument : the noderef pointing to "Company Home"
* second argument : an arraylist ; for example [User Homes, username, subfolder]

Apparently the code works as admin but not as a regular user.
As a regular user the method resolveNamePath throws a filenotfoundexception.

Help would be appreciated.

Re: Problem with getChildByName

derek — Wed, 18 Jun 2008 14:08:51 GMT

Do regular users have access to all elements of the path?

Re: Problem with getChildByName

kdejaeger — Wed, 18 Jun 2008 21:19:12 GMT

I found my stupid mistake.

For example user koen has home folder "Company Home/User Homes/koen".
And when using the resolveNamePath method (companyhome_noderef, list [User Homes, koen]), I got the error.

The rootnode is resolved like this:


User user = AuthenticationHelper.getUser(request, response);
NodeRef personRef = user.getPerson();
NodeRef homeRef = nodeService.getProperty(personRef, ContentModel.PROP_HOMEFOLDER);
‍‍‍‍‍

So since I was testing as root, I allways got the "Company Home" noderef as homefolder.
But as user koen, I get "Company Home/User Homes/koen"

However I didn't manage to get the "Company Home" noderef with the code you mentioned earlier.
Can you add another code sniplet that gets the actual "Company Home" noderef from the ChildAssociationRef you mentioned earlier?

Right now I am using an xpath query "cm:name" equals "Company Home" to get this noderef.

Re: Problem with getChildByName

derek — Wed, 18 Jun 2008 22:43:05 GMT

Inject these properties (from repository.properties😞


spaces.store=workspace://SpacesStore
spaces.company_home.childname=app:company_home
‍‍‍‍

So:


\\ in setter: StoreRef spacesStoreRef = new StoreRef(spaceStore);
\\ in setter: QName companyHomePath = QName.createQName(namespaceService, spacesCompanyHomeChildName);
NodeRef workspaceStoreRootNode = nodeService.getRootNode(spacesStoreRef)
List<ChildAssociationRef> assocRefs = nodeService.getChildAssocs(workspaceStoreRootNode, ContentModel.ASSOC_CHILDREN, companyHomePath);
‍‍‍‍‍‍

It'll be much more efficient than the XPath cm:name query. You can then use the getChildByName query on the NodeService from Company Home downwards.

Re: Problem with getChildByName

kdejaeger — Thu, 19 Jun 2008 07:54:44 GMT

Ok thanks.

It seems the company home ref is found like this then.


   assocRefs.get(0).getChildRef(); //company home
‍‍‍

Thanks for the help.

Re: Problem with getChildByName

agatap — Fri, 20 Jun 2008 12:07:06 GMT

And if any other newbie like me wonders how to inject a value from a property file into a bean:
I have found a repository-properties bean in the core-services-context.xml (part of the config.jar).
It is backed by the PropertyPlaceholderConfigurer, a kind of postprocessing bean.


 <!– load common properties –>
    <bean id="repository-properties" 
          class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="ignoreUnresolvablePlaceholders">
            <value>true</value>
        </property>
        <property name="locations">
            <list>
                <value>classpath:alfresco/repository.properties</value>
                <value>classpath:alfresco/version.properties</value>
                <value>classpath:alfresco/domain/transaction.properties</value>
            </list>
        </property>
    </bean>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

To inject one of the property values from any of the files held by the repository-properties bean, you simply need to do add the following to your bean definition in the context.xml file:


   <!–  Injecting properties from the repository.properties config file –>
      <property name="companyHome" value="${spaces.company_home.childname}"/>
‍‍‍‍

… and of course rememer to define the setCompanyHome() method in your java class.
Best,
Agata

Re: Problem with getChildByName

agatap — Fri, 20 Jun 2008 14:54:18 GMT

I have problems following the example, where I inject the properties from repository.properties into my java code.
I am logged in as admin, and my java class is as follows:


public void setCompanyHome(String spacesCompanyHomeChildName){
      companyHomePath = QName.createQName( NamespaceService.APP_MODEL_1_0_URI, spacesCompanyHomeChildName);
   }
   
   public void setSpacesStore(String spaceStore){
      spacesStoreRef = new StoreRef(spaceStore);
   }
NodeRef getCompanyHomeFolder(){
      NodeRef workspaceStoreRootNode = nodeService.getRootNode(spacesStoreRef);
      List<ChildAssociationRef> assocRefs = nodeService.getChildAssocs(workspaceStoreRootNode, 
            ContentModel.ASSOC_CHILDREN, companyHomePath);
      NodeRef homeFolderRef = assocRefs.get(0).getChildRef();
      return homeFolderRef;
   }
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The problem is that assocRefs is empty - and I therefore have no childReferences 😞
Any ideas what went wrong here?
I work on 2.1C, with MySql.

Best regards
Agata

Re: Problem with getChildByName

derek — Mon, 23 Jun 2008 10:03:15 GMT

Can you show the values for spacesCompanyHomeChildName and the workspaceStoreRootNode.
Also, what is the result of:

select id, parent_node_id, child_node_id, type_qname, qname from alf_child_assoc limit 10‍

Re: Problem with getChildByName

agatap — Mon, 23 Jun 2008 13:28:02 GMT

I have solved the problem - the value of the injected properties is
spacesCompanyHomeChildName=app:company_home
workspaceStoreRootNode=SpacesStore

The problem was, that the QName needs to be created with a URI and a local name - ie without the "app:". In this case the hardcoded string will work:


QName.createQName(NamespaceService.APP_MODEL_1_0_URI, "company_home");
‍‍‍

-this gives the QName {http://www.alfresco.org/model/application/1.0}company_home.

Trying to be DRY, and use Spring for dependency injections, I injected the nameSpaceDAO bean, and ended up with the following code - I dont know if its the easiest way to do it?


public void setSpacesStore(String spaceStore) {
      spacesStoreRef = new StoreRef(spaceStore);
   }

   public void setNameSpaceDAO(NamespacePrefixResolver prefixResolver) {
      this.prefixResolver = prefixResolver;
   }

   public void init() {
      companyHome = QName.createQName(spacesCompanyHomeChildName,
            prefixResolver);
      LOG.debug("Compnay home path = " + spacesCompanyHomeChildName
            + "QName of company home is now " + companyHome);
   }

NodeRef getCompanyHomeFolder() {
      NodeRef workspaceStoreRootNode = nodeService
            .getRootNode(spacesStoreRef);
      List<ChildAssociationRef> assocRefs = nodeService.getChildAssocs(
            workspaceStoreRootNode, ContentModel.ASSOC_CHILDREN,
            companyHome);
return assocRefs.get(0).getChildRef();
   }

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Now I have all other kind of problems, but its another story :roll:
Best,
Agata