Re: [DISCUSS] New annotation to identify Functions whose class hierarchy spans multiple jar files

*@Jared*- actually, I should mention that *Spring* too provides other infrastructure support to inspect byte code for certain Annotation meta-data without needed to load classes. Although, *Spring* uses ASM [1] given FCS did not exist at that time. *Spring* definitely needed this from 2.5 and

Re: [DISCUSS] New annotation to identify Functions whose class hierarchy spans multiple jar files

*@Jared* - yes, makes sense. Thanks for the reference to FCS. I am familiar with it and I am also aware that Geode is starting to use this in other capacities. *Regarding name...* The one thing I dislike about the name "RegisterFunction" is it implies some action will be performed by Geode (in

Re: [DISCUSS] New annotation to identify Functions whose class hierarchy spans multiple jar files

I can't even say "RegisterableFunction" flibble flobble ;) On Fri, Aug 11, 2017 at 4:09 PM, Jared Stewart wrote: > Hi John, > > Thanks for the suggestions. I like “@RegisterableFunction” better than > “@RegisterFunction". I think that we don’t want @RegisterableFunction to

Re: [DISCUSS] New annotation to identify Functions whose class hierarchy spans multiple jar files

Hi John, Thanks for the suggestions. I like “@RegisterableFunction” better than “@RegisterFunction". I think that we don’t want @RegisterableFunction to be @Inherited, in order to avoid creating a new variant of the problem we are trying to fix. As you suggest, we should be mindful to

Re: [DISCUSS] New annotation to identify Functions whose class hierarchy spans multiple jar files

Hi Jared- In general, I like this idea since Annotations are a great form of meta-data and essentially meaningless outside of the intended context and therefore do not impose any adverse effects on any existing behavior. However, 2 things... 1 suggestion and 1 caution... 1. Perhaps