[infinispan-issues] [JBoss JIRA] (ISPN-7704) AbstractFileLookup#lookupFileStrict should also support absolute paths

[Sebastian Łaskawiec (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Łaskawiec updated ISPN-7704:
--------------------------------------
    Workaround Description: The only way is to create {{javax.cache.CacheManager}} Bean in Spring manually and specify. It is highly advised to use {{org.infinispan.jcache.embedded.JCacheManager#JCacheManager(java.net.URI, java.lang.ClassLoader, javax.cache.spi.CachingProvider, java.util.Properties)}} constructor for this.


> AbstractFileLookup#lookupFileStrict should also support absolute paths
> ----------------------------------------------------------------------
>
>                 Key: ISPN-7704
>                 URL: https://issues.jboss.org/browse/ISPN-7704
>             Project: Infinispan
>          Issue Type: Bug
>          Components: JCache, Spring Integration
>    Affects Versions: 9.0.0.Final
>            Reporter: Sebastian Łaskawiec
>            Assignee: Sebastian Łaskawiec
>            Priority: Critical
>
> When specifying {{spring.cache.jcache.config}} value in Spring's application.properties, Spring passes us a scheme with absolute path (e.g. {{file:/home/slaskawi/work/infinispan/CacheTest/target/classes/infinispan.xml}}). This causes problems with {{AbstractFileLookup#lookupFileStrict(java.net.URI, java.lang.ClassLoader)}} since it should construct a new {{File}} rather than load this resource from the classloader.
> Related Pull Request: https://github.com/infinispan/infinispan/pull/4474



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)