在Hibernate实体中使用AspectJ遇织入失效问题求助

Hey there, let's figure out why your aspect isn't kicking in on the PortOut Hibernate entity, even though it works fine on Spring-managed beans like @Service or @Component. Here's the breakdown and actionable fixes:

Why This Happens #

Hibernate creates and manages its entity instances through its own SessionFactory, not directly via the Spring container. Even with @Configurable on your entity, if the AspectJ weaving (via invesdwin-instrument) doesn't cover objects instantiated by Hibernate, your aspect won't intercept those method calls.

Step-by-Step Solutions #

1. Verify @Configurable is Properly Set Up #

@Configurable relies on AspectJ weaving (either compile-time or runtime) to work with non-Spring-managed objects. Make sure:

• You've enabled invesdwin-instrument's weaving for your entity package tr.com.example.model.porting — check your configuration to ensure this package is included in the weaving scope.
• Your Spring context has @EnableSpringConfigured enabled. This annotation is critical for Spring to support dependency injection and weaving on @Configurable classes.

2. Adjust Your Pointcut Expression #

The default execution() pointcut might not match methods on Hibernate-proxied entities. Try switching to a call() pointcut instead, which intercepts method invocations rather than internal execution:

@Around("call(* tr.com.example..PortOut.handleRequest(..))")
public void handlePortingProcessAdvice(ProceedingJoinPoint joinPoint) throws Throwable {
    joinPoint.proceed();
    log.debug("[POM]:{} is executed with parameters:{}", joinPoint.toShortString(), joinPoint.getArgs());
}

call() is often more reliable for intercepting methods on Hibernate proxy objects since it targets where the method is called, not just where it runs internally.

3. Ensure Your Entity Class is Weaved by invesdwin-instrument #

Double-check that invesdwin-instrument is actually weaving your PortOut class:

• Enable debug logging for invesdwin-instrument and look for logs indicating that tr.com.example.model.porting.PortOut is being weaved during application startup.
• You can also inspect the bytecode of your compiled PortOut class (using tools like javap) to confirm that aspect code has been injected.

4. Make Hibernate Use Spring to Create Entity Instances #

If you want entities to be fully Spring-managed (so aspects work like they do on @Service beans), configure Hibernate to delegate instance creation to Spring's BeanFactory:

• Use a custom Integrator or leverage Spring's SpringBeanContainer to hook into Hibernate's instance creation process.
• Alternatively, set hibernate.bytecode.provider=spring in your Hibernate configuration or register SpringSessionContext to tie Hibernate sessions to Spring's context.

Extra Tips #

• If you're using Hibernate lazy loading proxies, ensure your pointcut matches methods on the proxy class too. You might need to adjust the expression to include proxy classes (e.g., using within() or target() designators).
• Double-check version compatibility between invesdwin-instrument, Hibernate, and Spring — mismatched versions can cause weaving failures.

内容的提问来源于stack exchange，提问作者sarah