Re: open visibility of JavaClassCacheEntry

Fair enough, done in https://bz.apache.org/bugzilla/show_bug.cgi?id=62986 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: open visibility of JavaClassCacheEntry

On 06/12/2018 13:19, Romain Manni-Bucau wrote: > Hello Rémy, > > > Le jeu. 6 déc. 2018 à 14:13, Rémy Maucherat a écrit : > >> On Thu, Dec 6, 2018 at 11:51 AM Romain Manni-Bucau >> wrote: >> >>> Hi guys, >>> >>> can you make ContextConfig.JavaClassCacheEntry public please? Idea is to >> be >>>

Re: open visibility of JavaClassCacheEntry

Hello Rémy, Le jeu. 6 déc. 2018 à 14:13, Rémy Maucherat a écrit : > On Thu, Dec 6, 2018 at 11:51 AM Romain Manni-Bucau > wrote: > > > Hi guys, > > > > can you make ContextConfig.JavaClassCacheEntry public please? Idea is to > be > > able to override ContextConfig and potentially customize >

Re: open visibility of JavaClassCacheEntry

On Thu, Dec 6, 2018 at 11:51 AM Romain Manni-Bucau wrote: > Hi guys, > > can you make ContextConfig.JavaClassCacheEntry public please? Idea is to be > able to override ContextConfig and potentially customize processAnnotations > methods. Currently it is a pain and it is preventing to upgrade

Re: open visibility of JavaClassCacheEntry

PS: alternative which can be saner would be to split webConfig() in a set of small protected methods instead of a monolitic block, typically here a processAnnotations(webXmls) not depending on internals can work Romain Manni-Bucau @rmannibucau | Blog

open visibility of JavaClassCacheEntry

Hi guys, can you make ContextConfig.JavaClassCacheEntry public please? Idea is to be able to override ContextConfig and potentially customize processAnnotations methods. Currently it is a pain and it is preventing to upgrade meecrowave and likely tomee to java11+jlink support Romain Manni-Bucau