Missing proxy for calling local annotated methods

[KazzmanK]

Hi! I'm looking for an explanation of best practices, how it was originally considered by developers.
If I have a chain of calls Controller->ClassA.nonAnnotatedMethod->ClassA.annotatedMethod->Repository there will be no proxy specified by annotation, i.e. @transactional or @retryable.
To make annotations effective I need to create separate class Controller->ClassA.nonAnnotatedMethod->ClassB.annotatedMethod->Repository and make sure, that FIRST method called in class must be annotated.
This leads me to have some tools to analyze and warn. Or have all non-annotated methods private, or something. And using annotations becomes dangerous, requires extra specific tests just to make sure annotations are processed right.
Is this an expected behavior or I'm missing something significant?

[remeio]

This is an expected behavior.

ClassA.nonAnnotatedMethod->ClassA.annotatedMethod means ClassA.nonAnnotatedMethod->this.annotatedMethod.

this is not the proxy object.

see more aop-understanding-aop-proxies or Stackoverflow

[bclozel]

Thanks @remeio