On Fri, Dec 29, 2017 at 2:34 PM Steve Ebersole wrote:
> On Fri, Dec 22, 2017 at 5:33 AM Steve Ebersole
> wrote:
>
>>
>> * When using ByteBuddy as the byte code provider, I still needed to have
>>> Javassist around, as it's used in ClassFileArchiveEntryHandler. I
>>> understand that eventually th
I started playing around with possibly removing the need for
BytecodeProvider to be configured per-ClassLoader[1]. In fact I got a
working solution for allowing all 3 remaining ClassLoader-wide settings
per-application:
1. Whether to handle binary/lob data via streams - I was able to make
