|
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
|
|
<?xml-stylesheet type="text/xsl" href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
|
|
|
|
|
<ivy-module
|
|
|
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
|
|
|
xsi:noNamespaceSchemaLocation="http://incubator.apache.org/ivy/schemas/ivy.xsd"
|
|
|
|
|
version="1.3">
|
|
|
|
|
|
|
|
|
|
<info organisation="org.springframework" module="${ant.project.name}">
|
|
|
|
|
<license name="Apache 2.0" url="http://www.apache.org/licenses/LICENSE-2.0"/>
|
|
|
|
|
</info>
|
|
|
|
|
|
|
|
|
|
<configurations>
|
|
|
|
|
<include file="${spring.build.dir}/common/default-ivy-configurations.xml"/>
|
|
|
|
|
<conf name="commons-logging" extends="runtime" description="JARs needed to run with Commons Logging"/>
|
|
|
|
|
<conf name="aspectj" extends="runtime" description="JARs needed to run with AspectJ"/>
|
|
|
|
|
<conf name="context" extends="runtime" description="JARs needed to register @Configuration classes and @Bean methods"/>
|
|
|
|
|
<conf name="tx" extends="runtime" description="JARs needed to run transactional aspects"/>
|
|
|
|
|
<conf name="orm" extends="runtime" description="JARs needed to compile JPA aspects"/>
|
|
|
|
|
<conf name="cache" extends="runtime" description="JARs needed to compile caching aspects"/>
|
|
|
|
|
</configurations>
|
|
|
|
|
|
|
|
|
|
<publications>
|
|
|
|
|
<artifact name="${ant.project.name}"/>
|
|
|
|
|
<artifact name="${ant.project.name}-sources" type="src" ext="jar"/>
|
|
|
|
|
<artifact name="license" type="license" ext="txt"/>
|
|
|
|
|
<artifact name="notice" type="notice" ext="txt"/>
|
|
|
|
|
</publications>
|
|
|
|
|
|
|
|
|
|
<dependencies>
|
|
|
|
|
<dependency org="net.sourceforge.cglib" name="com.springsource.net.sf.cglib" rev="2.2.0" conf="test->runtime"/>
|
|
|
|
|
<dependency org="org.apache.commons" name="com.springsource.org.apache.commons.logging" rev="1.1.1" conf="compile, commons-logging->compile"/>
|
|
|
|
|
<dependency org="org.aspectj" name="com.springsource.org.aspectj.weaver" rev="${aspectj.version}" conf="optional, aspectj->compile"/>
|
|
|
|
|
<dependency org="org.springframework" name="org.springframework.beans" rev="latest.integration" conf="test->compile"/>
|
|
|
|
|
<dependency org="org.springframework" name="org.springframework.transaction" rev="latest.integration" conf="optional, tx->compile"/>
|
|
|
|
|
<dependency org="org.springframework" name="org.springframework.orm" rev="latest.integration" conf="optional, orm->compile"/>
|
|
|
|
|
<dependency org="org.springframework" name="org.springframework.test" rev="latest.integration" conf="test->runtime"/>
|
|
|
|
|
<dependency org="org.springframework" name="org.springframework.context" rev="latest.integration" conf="context->compile"/>
|
|
|
|
|
<dependency org="org.springframework" name="org.springframework.context.support" rev="latest.integration" conf="optional, cache->compile"/>
|
|
|
|
|
<dependency org="javax.persistence" name="com.springsource.javax.persistence" rev="1.0.0" conf="optional, orm->compile"/>
|
|
|
|
|
<dependency org="org.junit" name="com.springsource.org.junit" rev="${junit.version}" conf="test->compile"/>
|
Support executor qualification with @Async#value
Prior to this change, Spring's @Async annotation support was tied to a
single AsyncTaskExecutor bean, meaning that all methods marked with
@Async were forced to use the same executor. This is an undesirable
limitation, given that certain methods may have different priorities,
etc. This leads to the need to (optionally) qualify which executor
should handle each method.
This is similar to the way that Spring's @Transactional annotation was
originally tied to a single PlatformTransactionManager, but in Spring
3.0 was enhanced to allow for a qualifier via the #value attribute, e.g.
@Transactional(ptm1)
public void m() { ... }
where ptm1 is either the name of a PlatformTransactionManager bean or
a qualifier value associated with a PlatformTransactionManager bean,
e.g. via the <qualifier> element in XML or the @Qualifier annotation.
This commit introduces the same approach to @Async and its relationship
to underlying executor beans. As always, the following syntax remains
supported
@Async
public void m() { ... }
indicating that calls to #m will be delegated to the default executor,
i.e. the executor provided to
<task:annotation-driven executor=.../>
or the executor specified when authoring a @Configuration class that
implements AsyncConfigurer and its #getAsyncExecutor method.
However, it now also possible to qualify which executor should be used
on a method-by-method basis, e.g.
@Async(e1)
public void m() { ... }
indicating that calls to #m will be delegated to the executor bean
named or otherwise qualified as e1. Unlike the default executor
which is specified up front at configuration time as described above,
the e1 executor bean is looked up within the container on the first
execution of #m and then cached in association with that method for the
lifetime of the container.
Class-level use of Async#value behaves as expected, indicating that all
methods within the annotated class should be executed with the named
executor. In the case of both method- and class-level annotations, any
method-level #value overrides any class level #value.
This commit introduces the following major changes:
- Add @Async#value attribute for executor qualification
- Introduce AsyncExecutionAspectSupport as a common base class for
both MethodInterceptor- and AspectJ-based async aspects. This base
class provides common structure for specifying the default executor
(#setExecutor) as well as logic for determining (and caching) which
executor should execute a given method (#determineAsyncExecutor) and
an abstract method to allow subclasses to provide specific strategies
for executor qualification (#getExecutorQualifier).
- Introduce AnnotationAsyncExecutionInterceptor as a specialization of
the existing AsyncExecutionInterceptor to allow for introspection of
the @Async annotation and its #value attribute for a given method.
Note that this new subclass was necessary for packaging reasons -
the original AsyncExecutionInterceptor lives in
org.springframework.aop and therefore does not have visibility to
the @Async annotation in org.springframework.scheduling.annotation.
This new subclass replaces usage of AsyncExecutionInterceptor
throughout the framework, though the latter remains usable and
undeprecated for compatibility with any existing third-party
extensions.
- Add documentation to spring-task-3.2.xsd and reference manual
explaining @Async executor qualification
- Add tests covering all new functionality
Note that the public API of all affected components remains backward-
compatible.
Issue: SPR-9443
Backport-Issue: SPR-6847
Backport-Commit: ed0576c1811bbb3a17e2e9aed2810dc3c9097a09
13 years ago
|
|
|
<dependency org="org.hamcrest" name="com.springsource.org.hamcrest" rev="1.1.0" conf="test->compile"/>
|
|
|
|
|
<dependency org="javax.mail" name="com.springsource.javax.mail" rev="1.4.0" conf="optional, test->compile"/>
|
|
|
|
|
</dependencies>
|
|
|
|
|
|
|
|
|
|
</ivy-module>
|
