Hi Adrian, we looked into this and still decided to have a component entity which is loaded with the run-install command and can be connected with a tenant of which the seed/demo data is loaded. Because the tenants are already in a entity it would be easier to have the components there too.
we use this feature in an automated test and demo environment. the commit is in: revision 1172989. Regards, Hans On Mon, 2011-09-05 at 08:33 +0100, Adrian Crum wrote: > I would prefer a new attribute or element in the ofbiz-component.xml > file that controls tenant loading of webapps/data. > > -Adrian > > On 9/5/2011 7:46 AM, Hans Bakker wrote: > > Currently we have: > > > > load-tenant-data-readers > > Loads data of given data-readers in the tenant database > > run-tenant-install-file > > Loads the data of the tenant using the command line argument > > 'file' to load data from a given file > > > > > > How about adding an optional 'tenant' parameter to the: > > ./ant run-install > > ./ant run-install-seed > > commands? > > > > At the same time we would like to add a TenantComponent entity which > > lists all components which are specific for a tenant. > > > > The above 2 commands 'run-install' and run-install-seed will (when a > > tenant is specified) import the requested data files from all components > > which are not assigned to a tenant and data files of the components of > > the requested tenant. > > > > Please provide your input. > > -- Ofbiz on twitter: http://twitter.com/apache_ofbiz Alternative ofbiz website: http://www.ofbiz.info http://www.antwebsystems.com : Quality services for competitive rates.
