[
https://issues.apache.org/jira/browse/OFBIZ-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337222#comment-14337222 ]
Jacques Le Roux commented on OFBIZ-5757:
----------------------------------------
Hi Deepak,
I recently tried to use
ant load-tenant
and [the result were not as expected|
https://issues.apache.org/jira/browse/OFBIZ-6071?focusedCommentId=14320876]
Pierre says that
./ant create-tenant
and
./ant load-tenant-data-readers
are enough and I tend to agree due to this experience. The tenant targets are too much and confusing. So I'd like to remove all *main* tenant targets (those documented) but those 2.
Pierre, I wonder about the work done for OFBIZ-3971, still valid right? But then should we keep load-tenant-admin-user-login as a main tenant target?
> Remove tenant data from the demo data set
> -----------------------------------------
>
> Key: OFBIZ-5757
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5757> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Jacques Le Roux
> Priority: Minor
> Labels: tenant
> Attachments: OFBIZ-5757-TenantCleanup.patch
>
>
> The demo data set (in location /framework/entity/data/TenantDemoData.xml) contains elements to load the tenants DEMO1 and DEMO2 into the implemented OFBiz setup.
> This data set is intended to be loaded into the master tables when a user wants to explore multity tenancy. However, when a user also wants/needs to load demo data into the tenant DEMO1 or DEMO2 OFBiz also tries to upload the demo setup data for each tenant. This is not allowed as tenants do not have access to tables:
> # Tenant
> # Tenantdatasource
> # etc
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
