Fixed issue 29894: Merged [gsi-removal] project

http://wiki.openbravo.com/w/index.php?title=Projects:OpenID_Removal

[gsi-removal] Change 'Iterator' to 'for' loop in Login.java

[gsi-removal] Update classpath template with the removed sources

[gsi-removal] Update license with the removed libraries

[gsi-removal] Restored AD_TABLE and AD_COLUMN of the removed modules
to avoid warnings during the export.database

[gsi-removal] Added 'service.integration.google' and 'service.integration.openid' modules:

In order to avoid problems with localization modules having dependencies to these ones,
a basic version of them have been restored

[gsi-removal] Removed 'service.integration.google' and 'service.integration.openid' modules:

- Removed source files
- Added a 'Module Merge' in 'v3 Framework' module. It also includes the merge that
was contained in 'service.integration.openid' to avoid problems while upgrading
from a very old Openbravo 3 version
- Removed the dependencies of these modules from 'v3' module
- Removed 'accesses' registered in sampledata to windows/views provided by the removed modules

[gsi-removal] Modified Login to use the new stuff:

Now, 'out of the box', the Google Sign In icon is just informative.
In order to make it runs, the 'Google Sign In' module (Professional) should be insalled

[gsi-removal] Added new Google Sign In icon

[gsi-removal] Added new messages

[gsi-removal] Moved 'OBSEIG_ShowGIcon' preference to 'client.application'

[gsi-removal] Moved 'guice', 'httpclient', 'httpcore' and 'httpmime' libraries to 'client.application'

CI: merge back from main

CI: update AD_MODULE to version 26651

related to issue 29751: fixed success status when executing bg processes

When a background process finsished successfully its status was incorrectly
set to error instead of success

CI: merge back from main

CI: update AD_MODULE to version 26647

Fixes issue 29896: Prevents unneded datasource request when filtering

When the grid was filtered in a scrolled down grid, two datasource requests to load the grid were being done instead of one. This happened due to two reasons:
- The function scrollTo of the grid's body was being invoked while the grid was being filtered. This function can be skipped in this case because when a datasource request is triggered due to a filter event, the grid is always automatically scrolled up to the top
- If the OBViewGrid.getRecord function was invoked in the middle of a datasource request, an additional request was done. To prevent this, in this case the function returns Array.LOADING

To detect if the grid is in the process of doing a datasource request, the isFilteringExternally flag is used. This flag is set in the handleFilterEditorSubmit function, and only if the change in the filter editor is going to trigger a datasource request. The flag is reset in the callback of that function.

This previous fix did not work properly, as the criteria passed to the willFetchData function was not proper, it needed to the processed in the convertCriteria function.

Related to bug 29256: Code Review

Add coalesce in case there is no batch associated to set GL Journal Org, in order to avoid issues in the if condition done right after the query if null values are compared

Fixes issue 29256: Error while completing a Simple G/L Journal in Oracle

A query in gl_journal_post has been changed to avoid errors in Oracle when retrieving a null id

Fixes issue 27170: Performance problems in CharacteristicValueEventHandler

onUpdate method has been changed to execute an update query instead of two OBCriteria queries, which improves the performance of the event handler.

CI: merge back from main

CI: update AD_MODULE to version 26642

Related with issue 29896: Fix backed out because it is breaks int-initial tests

A side effect of the changeset is making Selenium unable to know when a grid has been loaded under certain circumstances.

Fixes issue 29897: False positives in GLJournalAccountingCheck validation
Missing ad_table_id constraint ends up in wrong validation when there are old records using numeric values for ids.

Related to issue 29766: Retail Operations Buffer: store all transactions in operations table before processing
Solve javadoc errors

Fixes issue 29896: Prevents unneded datasource request when filtering

When the grid was filtered in a scrolled down grid, two datasource requests to load the grid were bein
g done instead of one. This happened due to two reasons:
- The function scrollTo of the grid's body was being invoked while the grid was being filtered. This f
unction can be skipped in this case because when a datasource request is triggered due to a filter eve
nt, the grid is always automatically scrolled up to the top
- If the OBViewGrid.getRecord function was invoked in the middle of a datasource request, an additiona
l request was done. To prevent this, in this case the function returns Array.LOADING

To detect if the grid is in the process of doing a datasource request, the isFilteringExternally flag
is used. This flag is set in the handleFilterEditorSubmit function, and only if the change in the filt
er editor is going to trigger a datasource request. The flag is reset in the callback of that function
.

CI: merge back from main

CI: update AD_MODULE to version 26633

ted to issue 29751: Killable processes

Few minor enhacements:
- When a process is killed, its status in process monitor is shown as "Killed
by User"
- When user clicks on "Kill Process" button change the message from "Process
killed successfully" to "Kill signal sent to process" as sending the kill
signal doesn't imply necessaryly the process to be successfully killed
- Changed UI message levels when "Kill Process" button is clicked:
- If signal is sent: from success to info
- If process does not implement KillableProcess: from info to warn
- Added ProcessBundle to KillableProcess.kill method so process instance's
information can be accessed (ie. allows to add extra log when killing the
process)