Security is now by default not loaded because not part of seed anymore this will make all component hidden and not accessible .
It is still loaded as part of the reader 'demo'
to load the security files:
./ant load-readers -Ddata-readers=security
Now it is possible to load only a selection of the security files in your hot-deploy component as follows:
<entity-resource type=data reader-name=seed loader=main location=../../framework/security/data/SecurityData.xml/>
<entity-resource type=data reader-name=seed loader=main location=../../framework/webtools/data/WebtoolsSecurityData.xml/>
<entity-resource type=data reader-name=seed loader=main location=../../applications/party/data/PartySecurityData.xml/>
This will enable only standard groups, the party and the webtools application.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1346255 13f79535-47bb-0310-9956-ffa450edef68
About the issue I got. I simply forgot to update my XML catalogs after having changed the OFBiz working copy reference name.
Thanks to Paul Piper for his help about this last point, by pointing about XSD reference.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1234014 13f79535-47bb-0310-9956-ffa450edef68
debugResources is true which creates a DebugXAResource (that creates an Exception) , it should be false and made an option for debuging
jleroux: see comments in Jira 4282 for more
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1226234 13f79535-47bb-0310-9956-ffa450edef68
XmlFileLoader: File file:.....framework/entity/config/entityengine.xml process fatal error. Line: 686. Error message: Invalid byte 2 of 2-byte UTF-8 sequence.
After having manually put back the line modified by an automatically applied patch, I got this mis-representation. Not sure why, and anyway had no chances to think about it (certainly due to a difference on how UTF-8 was represented on these servers and on my machine - XP with Putty and SSH)
So I remove this weirdness to prevent future possible nervous crises ;o)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1104173 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
This patch provides the fundamentals to resolve an issue where the sorting of null values were inconsistent (sometimes sorting first and other times sorting last). Specifically, this patch allows one to create an order-by clause via any of the order-by elements of "-myField NULLS LAST" where this text parses out the - (as descending) and the "nulls last".
Since not all databases support the "nulls" argument on an order by clause (it was introduced as part of the OLAP support specification) , our entity-engine.xml file allows each data source to indicate if it has this support. If the support does not exist and nulls first/last is specified, the sql that is generated uses native sql to simulate the nulls first/last intent. At this time, the derby, postgres, and oracle databases are marked to use the nulls first grammar.
Right now, if you do not specify "NULLS XXX" in the field-name for the order-by it makes no change whatsever (naturally this assumption could be changed to have a default).
It should be noted, that my intent here was ultimately to "properly" model the order by into something whose xml representation could look something like ...
<entity-order-by field-name="fieldName" ascending="true" nulls-first="true" />
Divesh Dutta added a comment - 07/May/10 01:44 AM HI Bob, This patch works as expected for derby, postgres, and oracle databases as you have already mentioned. Cant we have some generic solution which supports all the databases. Or we can have some conditional code, where we can check which datasource is being used, and then generate the sql accordingly. Please let me know your views on this.
Bob Morley added a comment - 07/May/10 08:07 AM
Hi Divesh,
I added a more detailed description in the forum thread; but in brief this is a generic solution which supports all databases which generates the sql accordingly. What this patch does not do is apply a standard default order for all databases; it just adds support for one to dictate how they want the nulls sorted.
For example, when one sets the order-by they can set it to "lastName DESC NULLS FIRST" which should apply to all databases.
The thread Bob was referring above ends at http://markmail.org/message/47z7fwtawehuem6b
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@950901 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
For now everything is in a separate specialpurpose component to facilitate the community review but as soon as everything will be consolidated the component will probably disappear (absorbed by the existing framework/applications components).
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@584727 13f79535-47bb-0310-9956-ffa450edef68
Two working connection factories are included now, Minerva and DBCP.
Minerva is still default until more testing can be done on DBCP; to change this use the DBCPConnectionFactory instead of MinervaConnection factory (see entityengine.xml)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@575396 13f79535-47bb-0310-9956-ffa450edef68