ResourceMerger : Resolve the nodes in two steps
authorVishesh Handa <handa.vish@gmail.com>
Fri, 8 Jul 2011 15:56:58 +0000 (21:26 +0530)
committerVishesh Handa <handa.vish@gmail.com>
Fri, 8 Jul 2011 15:56:58 +0000 (21:26 +0530)
commit750579f1d9c9b7017bccc2113f5290310d8946b7
treed0daa6e72ee593039ddcf85c614b041ed035f227
parent2ca96b93a93d3dd914eda427901fae13a7676c3c
ResourceMerger : Resolve the nodes in two steps

Initially resolve all the mapped (identified) nodes, then perform
all the max cardinality and domain/range checks. Only after that
should the unmapped nodes be created.

Before this, the nodes were only resolved after the cardinality and
domain range checks. This resulted in the domain range checks
occasionally failing if the required type was in the store.

This fixes : testStoreResources_correctDomainInStore2
             testStoreResources_correctRangeInStore2

Resolving a node => changing it's uri to the identified resource
nepomuk/services/storage/resourcemerger.cpp
nepomuk/services/storage/resourcemerger.h