Alternatives for Active Objects and ApplicationProperties

[Mik Wawrzyniak]

Hello,

We would like to start the process of adapting our plugin to JIRA Data Center.

Currently, the plugin uses Active Objects and ApplicationProperties to store various user settings and information.

I would like to ask for information if Active Objects and ApplicationProperties can still be used, and if not, is there any suggested alternative for them?

Regards,
Mik

[Maciej Swinarski]

Hi,

I would suggest using AO with a cache (replicated by invalidation). 

public SomeManager(CacheManager cacheManager) {  
    cache = cacheManager.getCache( 
       getClass().getName() + ".cache", //cache name     
       this::loadValueForKey, //cache loader backed by AO
       new CacheSettingsBuilder()
         .remote()
         .replicateViaInvalidation()
         .unflushable()
         .build(); // cache replicated via invalidation
) 

Depending on amount of data and usage pattern ApplicationProperties may not be optimal (underlying data store based on the OfBiz PropertySet, shared db structure and cache between all other PropertySet clients).

Regards,

Mac

[Mik Wawrzyniak]

Hi Mac, thanks for the quick reply.

There is very little data saved with AO.
Only one entity interface and just a few values (plug-in settings) saved with ApplicationProperties. Are changes also suggested in this case?

Regards,

Mik