Details
-
Bug
-
Resolution: Done
-
Major
-
JBossAS-5.1.0.GA, 6.0.0.M1
-
None
Description
The setter for the scanEnabled property does not cache the value, it only uses it to cancel an already-started scheduled task. If the setter is called during bean configuration, there is no scheduled task, the setter essentially becomes a no-op, and when start() is called the task is scheduled.
Effect is the only way to disable HDScanner via configuration is to remove the deployment; you can't leave it deployed but configure whether it is enabled (e.g. with a system property).
Attachments
Issue Links
- is incorporated by
-
JBPAPP-3234 Setting HDScanner's scanEnabled Attribute Via XML Should Work As Expected
- Resolved