weird, either it uses a different provider or it is ehcache specific.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2015-09-02 16:27 GMT+02:00 Steve Goldsmith <sgjava@gmail.com>:

> No, this is different. If I use the default configuration
> cachingProvider.getCacheManager() all is good. I can access the cache
> inside the service via cacheBean.getCacheManager().getCache("testCache").
> If I specify the configuration file location in getCacheManager I can no
> longer access the cache. It doesn't matter what classloader I pass either
> including the default.
>
> On Wed, Sep 2, 2015 at 2:15 AM, Romain Manni-Bucau <rmannibucau@gmail.com>
> wrote:
>
> > providers are by classloader, arent you in the same issue you got
> > previously?
> > Le 2 sept. 2015 04:00, "sgjava" <sgjava@gmail.com> a écrit :
> >
> > > Using system properties for ehcache.xml substitution will get me what I
> > > need
> > > for now. I updated my Github https://github.com/sgjava/jcache-tomee to
> > > reflect that. It's not ideal, but it allows me to configure RMI
> provider
> > > and
> > > listner (among other properties). It does not require any provider
> > specific
> > > code as well, so I should be able to plug in other implementations.
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://tomee-openejb.979440.n4.nabble.com/JCache-cache-manager-configuration-file-tp4676052p4676053.html
> > > Sent from the TomEE Users mailing list archive at Nabble.com.
> > >
> >
>
>
>
> --
> Steven P. Goldsmith
>