<task:executor/> cannot be used as an inner bean [SPR-6388]

[spring-projects-issues]

Dave Syer opened SPR-6388 and commented

task:executor/ cannot be used as an inner bean because its parser treats the id attribute as mandatory. If this can be fixed it would be useful.

---

Affects: 3.0 RC2

[spring-projects-issues]

Mark Fisher commented

The one thing we need to consider with this is how the thread name prefix would be determined. Normally the default is the bean name + "-pool-". For monitoring and management it's necessary to have a name. I see two options, either keep "id" as a required field but use it as the thread prefix only in the nested case, or else create the name from the owning bean's name + "-pool-".

[spring-projects-issues]

Juergen Hoeller commented

Good point. I guess the easiest solution would be to keep using id for the thread prefix and just to make sure that the element can still be used in a nested fashion. This would be similar to a plain nested <bean> then, which may have an id specified that the instance can receive through BeanNameAware; it just won't be registered as a named bean with the factory.

Juergen

[spring-projects-issues]

Dave Syer commented

That behaviour is probably already supported, right? I was just surprised that I was unable to remove the id when it was an inner bean.

[spring-projects-issues]

Juergen Hoeller commented

Alright, I'll add a test case for the nested scenario and will mention the semantics of the id value in the namespace documentation.

Juergen