Revamped InvocationPolicy

[KarelCemus]

• dropped implicit InvocationPolicy from Scala version of the API
• replaced by the instance configuration through the config file
• works also with JavaRedis

Relates to #147

[KarelCemus]

@tzimisce012 Could you review the changelog and the reference.conf if it would resolve the invocation policy issue? It works also with JavaRedis but it isn't configured per method invocation as it used to be but it is configured per cache instance instead.

[tzimisce012]

I'll do it tomorrow

[hparkerfly]

Hi Karel, regarding this:

  # note: this is global definition, can be locally overriden for each
  # cache instance. To do so, redefine this property
  # under 'play.cache.redis.instances.instance-name.this-property'.

I would like to ask how could we create several redis instances in a play project.

[KarelCemus]

Hi @hparkerfly, thanks for your question.

Please, do not contribute the offtopic questions to the issues and PR, either open a new ticket or email me.

Regarding your question, there is a sample project, which uses multiple named caches, i.e., multiple instances. Here, you can see the configuration. Notice the recovery: custom, this is the example how you override the global configuration.

[hparkerfly]

Thanks @KarelCemus!

[tzimisce012]

Everything works! I didn't know how to configure cache instances but I just read the sample project that you have. Thanks :)

[KarelCemus]

@tzimisce012 Great. Would it at least partially solve the issue you opened? #147

[tzimisce012]

Yes, indeed :)