We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Willi Wurzer opened SPR-6368 and commented
I have
<task:annotation-driven executor="myExecutor" scheduler="myScheduler" /> <task:executor id="myExecutor" pool-size="${task.executors}" /> <task:scheduler id="myScheduler" pool-size="${task.schedulers}" />
${task.schedulers} gets resolved, ${task.executors} not
SchedulerBeanDefinitionParser uses builder.addPropertyValue("poolSize", poolSize)
ExecutorBeanDefinitionParser parses the unresolved attribute String poolSize = element.getAttribute("pool-size");
Affects: 3.0 RC2
Referenced from: commits a6b6ba8
The text was updated successfully, but these errors were encountered:
Mark Fisher commented
Added TaskExecutorFactoryBean so that all pool-size range determination happens in the FactoryBean stage (after any property-placeholder resolution).
Sorry, something went wrong.
No branches or pull requests
Willi Wurzer opened SPR-6368 and commented
I have
<task:annotation-driven executor="myExecutor" scheduler="myScheduler" />
<task:executor id="myExecutor" pool-size="${task.executors}" />
<task:scheduler id="myScheduler" pool-size="${task.schedulers}" />
${task.schedulers} gets resolved, ${task.executors} not
SchedulerBeanDefinitionParser uses
builder.addPropertyValue("poolSize", poolSize)
ExecutorBeanDefinitionParser parses the unresolved attribute
String poolSize = element.getAttribute("pool-size");
Affects: 3.0 RC2
Referenced from: commits a6b6ba8
The text was updated successfully, but these errors were encountered: