* Allow to apply/reapply patches even when there are more than 3 patches in patches directory (it can be the case when you have other patches than those created with create-ofbiz-patches)
Note: the ant patch task will not work on Windows (diff in svn put Unix EOL into patch files), because there are no way to use the --binary parameter. So to have patches working in Windows you need to change their EOL to CR+LF (Eclipse, Notepad++ or Scite can do the trick)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1083087 13f79535-47bb-0310-9956-ffa450edef68
This patch enables users to create new tenants via the ANT process.
Users can enter:
* Tenant ID
* Tenant Name
* Data to load on creation of the tenant db (e.g.seed, seed-ext, demo)
* Database Platform (Derby, MySQL, Oracle, PostgreSQL) remark: You can NOT mix platforms)
* IP address of the database (you can add a port if needed)
* User-ID for the database
* Password for the database
Based on the data provided the process will:
* Create a new row in the Tenant table
* Create a new row in the TenantDataSource table
* Create new tables in the new tenant database and fill with initial data (seed, seed-ext, demo)
* Create a new admin id for the tenant (based on Tenant ID followed by '-admin')
* Set the initial password for the tenant admin id (initial 'ofbiz', must be changed on first login)
This patch has been tested against: Derby, MySQL, PostgreSQL. This has not been tested against other db platforms.
Prior to running the ANT task the user
* has to modify 'general.properties' in framework/common/config to reflect multi tenancy (multitenant=Y)
* has to have appropriate db driver(s) in place
* has to create the databases first in function of the entityengine.xml datasource-names (not for Derby, applicable for MySQL and PostgreSQL.)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1065144 13f79535-47bb-0310-9956-ffa450edef68
BJ: when there is an error, the control servlet looks for an error path in <param-name>allowedPaths</param-name>
it does not find one throwing an exception which buries the orginal error.
instead of changing the code it is just easier to add the /error: path.
then the real error gets reported correctly.
JLR: This will maybe help to better understand some errors on demo servers, and can't hurt
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@954135 13f79535-47bb-0310-9956-ffa450edef68
[ \t]+$ => "" (empty)
Should be easier to review when committing changes with trailing spaces removed automatically by anyedit or such tool (please refer to http://docs.ofbiz.org/x/mg)
Of course this effort to remove trailing spaces has no functional implications.
Actually, I was doing a 1st commit and as it's long to upload, I got conflicts with r763135
In the meantime I did some refactoring also in *.java and *.groovy files :
){ => ) {
if( => if (
while( => while (
}else => } else
else{ => else {
switch( => switch (
try{ => try {
}catch => } catch
catch( => catch (
}finally{ => } finally {
So these changes are also in this commit, should not be a problem anyway.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@763175 13f79535-47bb-0310-9956-ffa450edef68
firstvisit, after-login, before-logout, preprocessor and postprocessor elements. Events with same name will be overridden and only the last one will be executed. Overriding works also in cases when a controller.xml includes other controller files.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@761220 13f79535-47bb-0310-9956-ffa450edef68
ant create-component
You will be prompted for:
1) component name (e.g. "test")
2) component resource name (e.g. "Test")
3) webapp name (e.g. "testapp")
4) base permission (e.g. "TEST")
and the target will create the component in the hot-deploy folder.
Restart ofbiz and the new application will be up and running.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@741605 13f79535-47bb-0310-9956-ffa450edef68