Thu, 10 Aug 2017 08:49:37 +0200fixed bug 36359: can get stale cached WS user context
Asier Lostalé <asier.lostale@openbravo.com> [Thu, 10 Aug 2017 08:49:37 +0200] rev 32241
fixed bug 36359: can get stale cached WS user context

Don't invalidate cache on Preference modifications as they occur very often and,
in general, they shouldn't affect WS sessions.

Thu, 10 Aug 2017 08:47:31 +0200related to issue 36359: fixed related test case
Asier Lostalé <asier.lostale@openbravo.com> [Thu, 10 Aug 2017 08:47:31 +0200] rev 32240
related to issue 36359: fixed related test case

Test for preference to allow/disable unpaged datasource request was incorrectly
affected by WS user cache beacuse it was mixing WS and datasource request sessions.

Being PreferenceCache session scoped, it is not necessary to create Preference
through WS, it can be directly created in test as far as it is ensured DS request
is performed in a new session.

Fri, 28 Jul 2017 11:04:38 +0200fixed 36359: can get stale cached WS user context
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 28 Jul 2017 11:04:38 +0200] rev 32239
fixed 36359: can get stale cached WS user context

When invoking WS, user context is cached in order to prevent its (heavy)
creation on every request. This cache was not properly invalidated.

Changes to improve this invalidation:
1. Purge cache before trying to retrieve elements, not afterwards.
2. Cache elements already had a valid period of 30 minutes, but this period
was restarted everytime the element was used. Now the period starts when
the context is cached and it never gets reset.
3. In addition to this expiration time, ADUser.updated was checked when purging
cache, and if it was modified since it was cached, it was removed. This
implementation had some problems, that are now solved:
* ADUser is not the only (nor even the main) entity that when modified
can change permissions in cached contexts, therefore modifications in
any other entity (ie. Organization) were not triggering cache invalidataion.
A new EventObserver taking care of all entities that participate in the
permissions definition has been created to invalidate cache.
* For every WS request ADUser.updated for every cached context was checked
querying DB, adding some performance overhead (specially when many contexts
where already cached). As now invalidation occurs in memory, it is not
necessary to query DB anymore.

This mechanism provides a fully accurate cache when working in a single node.
In case of clustered environments, it is possible that caches kept in a node
different than the one modifying permissions to continue returning stale contexts,
but, as per topic 2, this is restricted to, at most, 30 minutes.

Tue, 01 Aug 2017 18:50:27 +0200Fixes issue 36537: Store the response of an action also in c_import_entry
Martin Taal <martin.taal@openbravo.com> [Tue, 01 Aug 2017 18:50:27 +0200] rev 32238
Fixes issue 36537: Store the response of an action also in c_import_entry
Add response info column to import entry and import entry archive

JsonUtils: prevent NPE in specific case
ImportEntryManager: set default error response in the response info field
src-db: added new columns, added to the window/tab and also set the ad_element

Wed, 09 Aug 2017 11:02:37 +0530Fixes issue 36619: Process Generate Invoices is not working with high volumes
Atul Gaware <atul.gaware@openbravo.com> [Wed, 09 Aug 2017 11:02:37 +0530] rev 32237
Fixes issue 36619: Process Generate Invoices is not working with high volumes

* Defined and used OBUI Selector Reference based reference for Sales Order parameter in Generate Invoice process.
* Implemented HQL where clause in the selector based on the validation C_Order SO to be invoiced.

Fri, 21 Jul 2017 07:48:49 +0200fixed 36527: OBException should not log itself by default
Asier Lostalé <asier.lostale@openbravo.com> [Fri, 21 Jul 2017 07:48:49 +0200] rev 32236
fixed 36527: OBException should not log itself by default

Changed default OBException behavior: now it only logs itself on creation if
explicitly set or if loger level is debug

Mon, 17 Jul 2017 09:55:17 +0200Fixed 36438. Removed unused variables from pl-functions & -triggers.
Aaron Calero <aaron.calero@openbravo.com> [Mon, 17 Jul 2017 09:55:17 +0200] rev 32235
Fixed 36438. Removed unused variables from pl-functions & -triggers.

That removes all unused variables in pl-code as found by plpgsql_check
warnings.

Tue, 30 May 2017 17:18:23 +0200related to issue 35994: create http session in stateful WS requests
Carlos Aristu <carlos.aristu@openbravo.com> [Tue, 30 May 2017 17:18:23 +0200] rev 32234
related to issue 35994: create http session in stateful WS requests

It was missing to create the http session for the stateful WS requests being in an environment with unlimited WS access

Tue, 30 May 2017 16:00:32 +0200related to issue 35994: code review improvements
Carlos Aristu <carlos.aristu@openbravo.com> [Tue, 30 May 2017 16:00:32 +0200] rev 32233
related to issue 35994: code review improvements
- No need to set in request this is a WS call, as webServicePostAuthenticate is only called for WS.
- Do not get list of expired modules for every single WS call.

Thu, 18 May 2017 12:30:55 +0200related to bug 35994: hide number of ws calls if the instance is unlimited
Carlos Aristu <carlos.aristu@openbravo.com> [Thu, 18 May 2017 12:30:55 +0200] rev 32232
related to bug 35994: hide number of ws calls if the instance is unlimited

Do not show the number of ws calls performed throughout the day in the "Instance Activation" window if the current instance has unlimited number of ws calls.