On 1/5/19 8:40 PM, Stefan Seelmann wrote: > Maybe it's the perfect time, because I'm struggling with using ApacheDS > with ehcache3 in Studio, OSGi related issues.
This is fixed now. I had to downgrade to version 3.5.3, see https://github.com/ehcache/ehcache3/issues/2554 for details. But I'd really prefer a simpler default cache solution :) > Also the server build now fails with Java 11. That's because ehcache 3 > uses JAXB (I assume to load XML config), but JAXB was removed from Java > SE in 11. Solution is to add JAXB dependency. Would be nice to avoid that. > > Kind Regards, > Stefan > > On 1/5/19 8:10 PM, Richard Sand wrote: >> Want me to open a pull request for jsr107 and a default caffeine impl? Or is >> this not the time >> >> -Richard >> >>> On Jan 5, 2019, at 1:42 AM, Emmanuel Lécharny <[email protected]> wrote: >>> >>> >>>> On 05/01/2019 03:05, Richard Sand wrote: >>>> Sorry I should have brought that up at the start! >>>> >>>> When have you planned to implement jsr-107? >>> >>> We haven't... This came quite late (2014) and we even haven't discussed >>> about it yet :-) >>> >>> >>> >>>> Having gone through this exercise, I think abstracting ehcache from the >>>> code is a good idea. >>> >>> I don't disagree. >>> >>> >>>> Also I checked out Caffeine and tested it in my company’s product, so far >>>> it seems good as a lightweight local cache fwiw. >>> >>> I do think it's probably what we should aim for, instead of using ehcache, >>> which is quite an elephant piece of code. >>> >>> As you realized, the cache is used pretty much everywhere in the server's >>> code, and changing it is not easy, but it's probably easier if we abstract >>> it. >>> >>> I don't have any prevention about such a change. >>> >>> >
