Dong Hyun Ko

I found out that the issue wasn't because of destruction and re-initialization of DataSource. Transactional feature doesn't seem to work with TypeORM's lazy relation feature.

I totally agree with your concern. But there are cases where it is not possible appying AOP with method decorator. For example, ```typescript @Injectable() export class SomeRepository extends Repository {...

Thank you for your suggestion! I agree that the way you suggested is much better than just using class decorator. I think I would change my code as you suggested....

I failed to understand _"Java decorators operate at compile time"_ because as far as I know, Java annotations are not functions and in Java/Spring environment the proxy beans for AOP...

I came up with an example. In circumstances where there are various AOP decorators to be applied in a certain order, class decorator could be problematic because AOP with method...

I believe Lombok works with annotation processor which is totally different from AOP. And spring-aop does support the feature!

This is a basic logging example with spring-aop. - annotation ```java @Target({ElementType.TYPE, ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) public @interface Logging { } ``` - aspect class ```java @Slf4j @Aspect @Component @Order(0) public class...

Oh, the code block about the cache that I mentioned in my first comment was just an example that I brought from the README of this project. I agree that...