[
https://issues.apache.org/jira/browse/SLING-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5064.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1705475
first implementation, we've to test it further if it works in all contexts
also added some missing resource resolver close calls in unit tests
> sling-mock: Register JCR node types for OSGi bundles in class path
> ------------------------------------------------------------------
>
> Key: SLING-5064
> URL: https://issues.apache.org/jira/browse/SLING-5064
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing Sling Mock Jackrabbit 0.1.4, Testing Sling Mock
> Oak 0.1.0, Testing Sling Mock 1.6.0
>
>
> for the resource resolver types "JCR_JACKRABBIT" and "JCR_OAK" node types are
> required to store data with certain nodetypes or query for it.
> if in the classpath OSGi bundles are present which define node type
> definitions in their {{Sling-Nodetypes}} bundle header they should be picked
> up and registered automatically in the repository.
> because the correct order of multiple bundles registering node types is not
> known it should try to re-register it multiple times (up to 5 times) to get
> the right order "by chance".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)