If a given Function uses a 3rd party dependency and they don't need to use that Function then I suppose it could save some system resources including PermGen space?
Normally, I'd respond by saying "well then don't include that Function in the jar that you're deploying." On Mon, Jan 9, 2017 at 4:21 PM, Dan Smith <dsm...@pivotal.io> wrote: > On Mon, Jan 9, 2017 at 4:18 PM, Kirk Lund <kl...@pivotal.io> wrote: > > > What about this use case: a user has a jar containing 100 Function > classes > > but only wants the deployer to register one of those, so they would still > > need some way to specify which classes to automatically instantiate and > > register during the deploy. Right now, it would register all 100 classes. > > > > Why would they not want to register all 100 functions? Is there any > negative impact from registering all of the functions in the jar? > > -Dan >
