Skip to content
New issue

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

PropertyPlaceholder Value not resolved with ExecutorBeanDefinitionParser ("Invalid pool-size value [${task.executors}]") [SPR-6368] #11034

Closed
spring-projects-issues opened this issue Nov 16, 2009 · 1 comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

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

@spring-projects-issues
Copy link
Collaborator Author

Mark Fisher commented

Added TaskExecutorFactoryBean so that all pool-size range determination happens in the FactoryBean stage (after any property-placeholder resolution).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant