[
https://issues.apache.org/jira/browse/SLING-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894878#action_12894878
]
Bertrand Delacretaz commented on SLING-1626:
--------------------------------------------
Looks like a timing/dependencies problem, with the following scenario the
content is loaded:
1. Start sling from scratch -> above error in log, no content loaded
2. Reload org.apache.sling.jcr.resource bundle -> sling namespace registered
3. Reload org.apache.sling.launchpad.content bundle -> content loaded
After that, > 300 integration tests pass, but not all of them (in revision
981845)
> Launchpad: NamespaceException: sling: is not a registered namespace prefix
> --------------------------------------------------------------------------
>
> Key: SLING-1626
> URL: https://issues.apache.org/jira/browse/SLING-1626
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: Launchpad Builder 6
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> Starting the standalone jar from launchpad/builder produces this error in the
> logs:
> org.apache.sling.jcr.contentloader.internal.ContentLoaderService activate:
> Problem while loading initial content and registering mappings for existing
> bundles
> javax.jcr.NamespaceException: sling: is not a registered namespace prefix.
> which (obviously) prevents many features from working
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
