[
https://issues.apache.org/jira/browse/JCRVLT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939963#comment-14939963
]
angela edited comment on JCRVLT-99 at 10/1/15 3:28 PM:
-------------------------------------------------------
also looked at {{ZipVaultPackage}} but didn't see an easy way to have the
{{InstallContextImpl}} not created with the root node as there doesn't see to
be a way to pass in the install context root path and don't feel familiar
enough the related feature set to introduce it... [~tripod], what would be the
impact if the root node is not accessible? would it work _if_ the install
context was not the root or are the many other dependencies that additionally
assume that that the ctx is bound to the root?
same for the other remaining usages.
was (Author: anchela):
also looked at {{ZipVaultPackage}} but didn't see an easy way to have the
{{InstallContextImpl}} not created with the root node as there doesn't see to
be a way to pass in the install context root path and don't feel familiar
enough the related feature set to introduce it... [~tripod], what would be the
impact if the root node is not accessible? would it work _if_ the install
context was not the root or are the many other dependencies that additionally
assume that that the ctx is bound to the root?
> Creating a package using package manager API requires read access to root node
> ------------------------------------------------------------------------------
>
> Key: JCRVLT-99
> URL: https://issues.apache.org/jira/browse/JCRVLT-99
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: Packaging
> Reporter: Marc Pfaff
> Attachments: JCRVLT-99_DefaultWorkspaceFilter.patch,
> JCRVLT-99_DocViewSAXImporter_JcrSysViewTransformer.patch,
> JCRVLT-99_Importer.patch, JCRVLT-99_JcrPackageDefinitionImpl.patch,
> JCRVLT-99_JcrPackageManagerImpl.patch, filevault_root_access.txt
>
>
> When creating a package using PackageManagerImpl.assemble() the package
> manager session used always requires read access to the root node, due to the
> call to Session.getRootNode().
> {code}
> Caused by: javax.jcr.AccessDeniedException: Root node is not accessible.
> at
> org.apache.jackrabbit.oak.jcr.session.SessionImpl$4.perform(SessionImpl.java:304)
> at
> org.apache.jackrabbit.oak.jcr.session.SessionImpl$4.perform(SessionImpl.java:298)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:209)
> at
> org.apache.jackrabbit.oak.jcr.session.SessionImpl.getRootNode(SessionImpl.java:298)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.getPackageRoot(JcrPackageManagerImpl.java:637)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.listPackages(JcrPackageManagerImpl.java:683)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.validateSubPackages(JcrPackageManagerImpl.java:490)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.assemble(JcrPackageManagerImpl.java:458)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageManagerImpl.assemble(JcrPackageManagerImpl.java:447)
> {code}
> I'm using version 3.1.20 (as reported by felix console), but somehow this
> version is not available in the Jira "Affects Version/s" field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
