From d6197b743da3e2042a20b0b83f9abaea09085dc5 Mon Sep 17 00:00:00 2001
From: Juergen Hoeller <jhoeller@vmware.com>
Date: Fri, 27 Nov 2009 01:45:53 +0000
Subject: [PATCH] clarified double role of id property

---
 .../springframework/scheduling/config/spring-task-3.0.xsd    | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/org.springframework.context/src/main/resources/org/springframework/scheduling/config/spring-task-3.0.xsd b/org.springframework.context/src/main/resources/org/springframework/scheduling/config/spring-task-3.0.xsd
index c929c71c26..2bb4c1de94 100644
--- a/org.springframework.context/src/main/resources/org/springframework/scheduling/config/spring-task-3.0.xsd
+++ b/org.springframework.context/src/main/resources/org/springframework/scheduling/config/spring-task-3.0.xsd
@@ -84,7 +84,10 @@
 				<xsd:annotation>
 					<xsd:documentation><![CDATA[
 	The bean name for the generated ThreadPoolTaskExecutor instance.
-	It will also be used as the default thread name prefix.
+	This value will also be used as the thread name prefix which is why it is
+	required even when defining the executor as an inner bean: The executor
+	won't be directly accessible then but will nevertheless use the specified
+	id as the thread name prefix of the threads that it manages.
 					]]></xsd:documentation>
 				</xsd:annotation>
 			</xsd:attribute>