| Key: |
SJC-86
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Chris Beams
|
| Reporter: |
Chris Beams
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Related
|
|
|
|
This issue is related to:
|
|
SJC-235
Remove deprecated setNamingStrategy() in favor of setBeanNamingStrategy()
|
|
|
|
|
|
|
|
It is currently only possible to specify / override the default BeanNamingStrategy when using XML to bootstrap JavaConfig. ConfigurationPostProcessor exposes a setNamingStrategy() setter. This should also be possible via JavaConfigApplicationContext / JavaConfigWebApplicationContext.
|
|
Description
|
It is currently only possible to specify / override the default BeanNamingStrategy when using XML to bootstrap JavaConfig. ConfigurationPostProcessor exposes a setNamingStrategy() setter. This should also be possible via JavaConfigApplicationContext / JavaConfigWebApplicationContext. |
Show » |
Sort Order:
| No work has yet been logged on this issue.
|
|
Cannot specify BeanNamingStrategy when using JavaConfigApplicationContext