Current there is on a "strict-max" implementation for pooling
That means grow until max and stay with this.
To destroy the instances directly you might remove the pool from your config. But the instances are created for each invocation.
If there is no initialization, I don't think you see much difference. Also it is possible to add pool config at Bean level by annotation.
Thank you Wolf-Dieter for that interessting idea.
I think in general bean pooling makes senese for my application, due to 24/7 usage of most beans.
Best would be like infinispan does: define max size and eviction after predefiend amount of idle time.
There are only particular beans i wan't to be destroyed when idle. Disable pooling could be an suitable solution too.
Do you think it would be possible to configure stateless bean pooling globaly via configuration and disable pooling for specific beans by annotation?
ok this seems to me that's not possible
The Annotation @Pool requiers an value.
Using a blank string will cause deployment errors.
This is very disapointing
You need to add the name of a valid strict-max pool