[7.0] Reduce invocation overhead for intercepted bean methods by AngeloRubens · Pull Request #3545 · weld/core

Do not create an InterceptionDecorationContext stack in client proxies when none exists

AngeloRubens

committed

a145543

Avoid ThreadLocal.remove() churn of the InterceptionDecorationContext stack

AngeloRubens

committed

37705ee

Avoid the container registry lookup on every client proxy invocation

AngeloRubens

committed

8d92a23

Reuse a per-thread InterceptionDecorationContext stack

AngeloRubens

committed

bf644c6

Skip the interception context lookup in client proxies until it is first used

AngeloRubens

committed

37a42bf

Resolve the contextual instance strategy of Weld beans without a type check in client proxies

AngeloRubens

committed

42b5dfb

Use a plain array for the per-thread InterceptionDecorationContext stack

AngeloRubens

committed

2f5a484

Invoke interceptor methods and the proceed method through method handles

AngeloRubens

committed

1c2b62c

Skip the per-call accessibility and interceptor method checks for cached interception chains

AngeloRubens

committed

5935514

Remember the interception chain of the first intercepted method of an instance

AngeloRubens

committed

b268c88

Remove the unused timer and constructor fields from around invoke invocation contexts

AngeloRubens

committed

799fb44

Do not allocate an empty arguments array for intercepted methods without parameters

AngeloRubens

committed

4d95fdd

Avoid the thread-local lookup in InvocationContext.proceed() on the invoking thread

AngeloRubens

committed

225a1f4

Preserve method access overrides in cached invokers and cover stack handoff

AngeloRubens

committed

c4a0dcc

Invoke simple methods through LambdaMetafactory generated functions

AngeloRubens

committed

76c1b6a

Apply access-override guard to lambda invokers

AngeloRubens

committed

6661eea

Apply Weld formatter output from CI to lambda access guard

AngeloRubens

committed

38f94f3

Navigation Menu

Repository navigation

[7.0] Reduce invocation overhead for intercepted bean methods - #3545

[7.0] Reduce invocation overhead for intercepted bean methods#3545
AngeloRubens wants to merge 17 commits into
weld:mainfrom
AngeloRubens:pr/proxy4-main

Commits on Oct 5, 2026

Do not create an InterceptionDecorationContext stack in client proxies when none exists

Avoid ThreadLocal.remove() churn of the InterceptionDecorationContext stack

Avoid the container registry lookup on every client proxy invocation

Reuse a per-thread InterceptionDecorationContext stack

Skip the interception context lookup in client proxies until it is first used

Resolve the contextual instance strategy of Weld beans without a type check in client proxies

Use a plain array for the per-thread InterceptionDecorationContext stack

Invoke interceptor methods and the proceed method through method handles

Skip the per-call accessibility and interceptor method checks for cached interception chains

Remember the interception chain of the first intercepted method of an instance

Remove the unused timer and constructor fields from around invoke invocation contexts

Do not allocate an empty arguments array for intercepted methods without parameters

Avoid the thread-local lookup in InvocationContext.proceed() on the invoking thread

Preserve method access overrides in cached invokers and cover stack handoff

Invoke simple methods through LambdaMetafactory generated functions

Apply access-override guard to lambda invokers

Apply Weld formatter output from CI to lambda access guard