Wed, 05 Jun 2013 14:03:22 +0200Fixes issue 23996: An event handler has been replaced with database constraints
Augusto Mauch <augusto.mauch@openbravo.com> [Wed, 05 Jun 2013 14:03:22 +0200] rev 20511
Fixes issue 23996: An event handler has been replaced with database constraints

The event handler TableDataOriginEventHandler has been replaced with database constraints. This is a better approach because it is simpler and easier to maint
ain.

The name of two of the messages has been updated so that it is the name as the constraint that throw them. The message used to warn the user that the table_name must be set if the data origin is 'Table' has been removed because now the table_name is mandatory again in the database.

Wed, 05 Jun 2013 12:36:15 +0200Fixes issue 23991: table_name column of ad_table table is mandatory again
Augusto Mauch <augusto.mauch@openbravo.com> [Wed, 05 Jun 2013 12:36:15 +0200] rev 20510
Fixes issue 23991: table_name column of ad_table table is mandatory again

At one point durint the development of the Datasource Based Tables project the table_name column of the ad_table table was set not mandatory, because this field was meant to be left empty for tables based on datasources. Later in the project it was decided to use the column 'name' (the name column of the Table table) to set the 'table_name' column for datasource based tables. This was we avoided having to change the table identifier (table_name).

After this change the table_name column must be mandatory in the database.

Tue, 04 Jun 2013 12:33:00 +0200Fixes issue 23975: Changes are only done when getValue() returns a string
Augusto Mauch <augusto.mauch@openbravo.com> [Tue, 04 Jun 2013 12:33:00 +0200] rev 20509
Fixes issue 23975: Changes are only done when getValue() returns a string

The numeric handling only needed to be done when getValue() returns a string, that is, when the user has entered a new value or modified the existing one. The textualValue needed to be set also.

Tue, 04 Jun 2013 10:20:19 +0200Fixes issue 23975: Number handling works using ',' as decimal separator
Augusto Mauch <augusto.mauch@openbravo.com> [Tue, 04 Jun 2013 10:20:19 +0200] rev 20508
Fixes issue 23975: Number handling works using ',' as decimal separator

In the fix of the issue 23758 [1] it was wrongly assumed that the function getValue() of a OBNumberItem was going to return a javascript number. When the an existing record has just been opened getValue() will return a number, but when the user edits it, it will return the string representation of the number using the format specified by the user.

Now this has been taken into account, so the value is treated differently if getValue returns a string or a javascript number.

[1] https://code.openbravo.com/erp/devel/pi/rev/2e4eccaa3cc8fc8ac434cb0d386166558d1ee686

Sat, 01 Jun 2013 01:56:07 +0200CI: update AD_MODULE to version 20506
RM packaging bot <staff.rm@openbravo.com> [Sat, 01 Jun 2013 01:56:07 +0200] rev 20507
CI: update AD_MODULE to version 20506

Fri, 31 May 2013 18:19:45 +0200Issue 23385: , Backed out: 6792989a9124
Stefan Hühner <stefan.huehner@openbravo.com> [Fri, 31 May 2013 18:19:45 +0200] rev 20506
Issue 23385: , Backed out: 6792989a9124
As is breaks OrgSetup when using the optional 'Location' field.

Fri, 31 May 2013 12:44:01 +0200Backout issue 0023929: In FIN_Financia_Account table the sequence number of
Jon Alegría <jon.alegria@openbravo.com> [Fri, 31 May 2013 12:44:01 +0200] rev 20505
Backout issue 0023929: In FIN_Financia_Account table the sequence number of
the identifier columns are not correctly defined

Fri, 31 May 2013 12:25:02 +0200Fixes issue 23385: Organization is generated even
Javier Etxarri <javier.echarri@openbravo.com> [Fri, 31 May 2013 12:25:02 +0200] rev 20504
Fixes issue 23385: Organization is generated even
if the Initial Org Setup ends with errors

Fri, 31 May 2013 12:13:27 +0200related to issue 23936: backout changeset 80ca7ee3ac68
Sandra Huguet <sandra.huguet@openbravo.com> [Fri, 31 May 2013 12:13:27 +0200] rev 20503
related to issue 23936: backout changeset 80ca7ee3ac68

Thu, 30 May 2013 16:56:01 +0200Related to issue 23770: Backed out change, some warning should be logged
Augusto Mauch <augusto.mauch@openbravo.com> [Thu, 30 May 2013 16:56:01 +0200] rev 20502
Related to issue 23770: Backed out change, some warning should be logged

The approach used in this fix (modifying the template so only the jasper error are logged by default) should be improved. Instead of not logging any warning, we should try to reduce the number of warnings logged by fixing them. I.e. lots of warnings are related to the use of deprecated methods, those can be avoided by using the @supresswarnings annotation or by using a not deprecated method.