为什么AspectJ编译时不编织Spring的@Configurable工作？ [英] Why doesn't AspectJ compile-time weaving of Spring's @Configurable work?

问题描述

更新5：我已经下载了基于最新Eclipse的最新Spring ToolsSuite IDE。当我将项目导入为Maven项目时，Eclipse / STS似乎使用Maven目标来构建我的项目。这意味着AspectJ最终在Eclipse中正常工作。

Update 5: I've downloaded the latest Spring ToolsSuite IDE based on the latest Eclipse. When I import my project as a Maven project, Eclipse/STS appears to use the Maven goals for building my project. This means AspectJ finally works correctly in Eclipse.

更新4：我最终只是使用Maven + AspectJ插件进行编译时编织，有效地绕过Eclipse的机制。

Update 4: I have ended up just using Maven + AspectJ plugin for compile-time weaving, effectively bypassing Eclipse's mechanism.

更新3：似乎AspectJ的Eclipse插件破坏了Eclipse正确发布到Tomcat的能力。只有删除项目中的AspectJ功能，才能让它再次正确发布。非常烦人。

Update 3: It seems AspectJ's Eclipse plug-in breaks Eclipse's ability to correctly Publish to Tomcat. Only by removing the AspectJ capability on a project can I get it to properly Publish again. Very annoying.

更新2：我现在正在使用Eclipse。这样说让我感到非常不舒服，但我不知道如何使用Eclipse或Maven构建它。这似乎是一个编译问题而不是运行时问题。

Update 2: I have this now working in Eclipse. It makes me very uncomfortable to say this, but I have no idea how I got it working from either Eclipse or Maven builds. It appears to be a compile issue rather than a run-time issue.

更新1：看来我已经通过Maven构建，但我不知道如何。 Eclipse仍然无法正常工作。我在 pom.xml 中唯一更改的是添加这些（无关紧要的？）配置参数：

Update 1: It appears I've gotten this to work via Maven builds, but I have no idea how. Eclipse still doesn't work. The only thing I changed in the pom.xml was adding these (insignificant?) configuration parameters:

<source>1.6</source>
<complianceLevel>1.6</complianceLevel>
<verbose>true</verbose>
<showWeaveInfo>true</showWeaveInfo>
<outxml>true</outxml>

我实际上担心我重复了这个问题，一切都不一致。随着我的了解，我会更新这个问题。

I'm actually worried that I have a repeat of this problem, where everything works inconsistently. I will keep this question updated as I learn more.

关于Eclipse，我通过采用我希望编织的二进制方面取得了一些进展 - 在这种情况下 spring-aspects.jar - 并将其从我的类路径中复制出来。然后我将这个外部jar添加到我的 Aspect Path 。执行此操作后，Eclipse在我的代码中正确显示了AspectJ标记。令人讨厌的是，我不能将 spring-aspects.jar 留在我的 Java Build Path 中，这是由Maven通过Maven插件为我维护的。但是，出于某种原因，AspectJ插件除非明确添加到 Aspect Path ，否则不会看到二进制方面。

With regards to Eclipse, I made some progress by taking the binary aspects I wish to weave - in this case spring-aspects.jar - and copying it out of my classpath. I then add this now external jar to my Aspect Path. After doing this, Eclipse properly shows me AspectJ markers in my code. It's annoying that I can't just leave spring-aspects.jar in my Java Build Path which is maintained by Maven for me via the Maven plug-in. For some reason, however, the AspectJ plug-in doesn't see the binary aspects unless they're explicitly added to the Aspect Path.

原帖： @Configurable是一个Spring注释，它允许将依赖项注入到Spring外部实例化的对象中（例如，通过Hibernate或某些Factory类） ）。

Original Post: @Configurable is a Spring annotation that allows dependencies to be injected into objects instantiated external to Spring (for example, by Hibernate or some Factory class).

我以前使用此注释进行加载时编织，主要是工作。偶尔我会启动，没有任何东西会被注入。此问题产生了此StackOverflow问题。答案并不多，但大多数建议我尝试编译时编织，因为可靠性更高。

I was using this annotation previously with load-time weaving and it mostly worked. Occasionally I would boot up and nothing would get injected. This issue spawned this StackOverflow question. There weren't many answers, but most suggested that I try compile-time weaving instead due to greater reliability.

我为Eclipse和Maven安装了AspectJ插件。这两者都产生了看似正确编译的类。我在AspectJ编译之前在文本编辑器中打开了其中一个类，但没有找到对AspectJ的引用。我在AspectJ编译后打开它，Eclipse和Maven生成的版本都引用了 org.aspectj.weaver.MethodDeclarationLineNumber 。这就是我认为它被正确编译的原因。问题是，一旦部署，就不会注入依赖项。

I installed the AspectJ plug-in for Eclipse and Maven. Both of these produce what appears to be properly compiled classes. I've opened up one of the classes in a text editor before AspectJ compilation and found no references to AspectJ. I opened it up after AspectJ compilation and both Eclipse and Maven generated versions have a reference to org.aspectj.weaver.MethodDeclarationLineNumber. This is why I assume it's being properly compiled. The problem is that once deployed, no dependencies get injected.

My Spring applicationContext.xml 包括以下内容：

My Spring applicationContext.xml does include the following:

    <context:spring-configured />

    <context:component-scan base-package="com.myapp" />

以上所有标记为@Configurable的类都需要完成DI吗？在从加载时编织到编译时编织的转换过程中，我删除了 META-INF / aop.xml ，< context：load-time-weaver /> 我的 applicationContext.xml ，以及我的 context.xml 中的Spring的Tomcat编织器。

Is the above all that's needed for classes marked @Configurable to have DI done? During the conversion from load-time weaving to compile-time weaving, I removed META-INF/aop.xml, <context:load-time-weaver /> from my applicationContext.xml, and Spring's Tomcat weaver from my context.xml.

如何调查此问题进一步？可能的原因是什么？

How can I investigate this problem further? What are possible causes?

推荐答案

它适用于我们使用编译时编织的maven，尝试添加以下插件：

It works for us on maven using compile time weaving, try adding the following plugins:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
    <compilerVersion>1.6</compilerVersion>
    <fork>true</fork>
    <source>1.6</source>
    <target>1.6</target>
</configuration>
</plugin>

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<executions>
    <execution>
        <id>compile</id>
        <configuration>
            <source>1.6</source>
            <target>1.6</target>
            <verbose>false</verbose>
            <outxml>true</outxml>
            <aspectLibraries>
                <aspectLibrary>
                    <groupId>org.springframework</groupId>
                    <artifactId>spring-aspects</artifactId>
                </aspectLibrary>
            </aspectLibraries>
        </configuration>
        <goals>
            <goal>compile</goal>
        </goals>
    </execution>
    <execution>
        <id>test-compile</id>
        <configuration>
            <source>1.6</source>
            <target>1.6</target>
            <verbose>false</verbose>
            <aspectLibraries>
                <aspectLibrary>
                    <groupId>org.springframework</groupId>
                    <artifactId>spring-aspects</artifactId>
                </aspectLibrary>
            </aspectLibraries>
        </configuration>
        <goals>
            <goal>test-compile</goal>
        </goals>
    </execution>
</executions>
<dependencies>
    <dependency>
        <groupId>org.aspectj</groupId>
        <artifactId>aspectjweaver</artifactId>
        <version>1.6.4</version>
    </dependency>
</dependencies>
</plugin>

它作为两个单独的执行步骤完成，允许您为单元测试和编译添加不同的方面库。

Its done as two separate execution steps to allow you to add different aspect libraries for unit testing and compilation.

您还需要为spring-aspects库添加以下依赖项：

You'll also need the following dependency added for the spring-aspects library:

    <dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-aspects</artifactId>
        <scope>compile</scope>
    </dependency>

这篇关于为什么AspectJ编译时不编织Spring的@Configurable工作？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！