[
https://issues.apache.org/jira/browse/OFBIZ-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271221#comment-13271221
]
Pierre Smits commented on OFBIZ-4836:
-------------------------------------
Hi Sascha,
Thanks for providing the patch to test the functionality.
After having applied it to a clean trunk checkout, doing a clean build and
install the demo-data and a modification to the 'ant create-tenant' target (and
process) to have it create the jcr settings in the database of the main
delegator in accordance with following example:
<JcrDataSource tenantId="@tenantId@" jcrMinRecordLength="0"
jcrRepHighlighting="1" jcrRepId="@tenantId@"
jcrRepPath="runtime/data/jcr/@tenantId@/"/>
I created a new tenant and saw the data in the JcrDataSource.
After subsequently restarting OFBiz and:
- logging in the main environment as admin I created a new entry in the
Jackrabbit section of the example application (that worked). I also uploaded
the patch into the repository successfully.
- having logged out and logged in again (but now as the tenant-admin in the
tenant environment I tried the same, but with no succes. It generated a NPE.
Looking thru the file/folder structure of OFBiz I didn't saw a jcr repository
created in location 'runtime/data/jcr/' for the tenant.
Did I miss a step?
Regards,
Pierre
> Jackrabbit (jcr) doesn't work nice with multi-tenancy aspect of OFBiz
> ---------------------------------------------------------------------
>
> Key: OFBIZ-4836
> URL: https://issues.apache.org/jira/browse/OFBIZ-4836
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Pierre Smits
> Priority: Blocker
> Fix For: SVN trunk
>
> Attachments: OFBIZ-4836-jcr-entity.patch, OFBIZ-4836_JCR_MultiTenancy
> .patch, jcr-config.xml
>
>
> When having multiple tenants and one of the users (of a tenant) creates
> (uploads) a file to JCR then this file is visible to all users of all tenants
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
