Hi Marc, hi all,
> The idea is that option A/B/C in the spec are *brain dead* it either
always
> refreshes or never refreshes... here we offer a simple way to specify a
> refresh time.
A feature I really would like to have is dynamic switching of
container commit options. This would enable good caching via A
most of the time, then switching to B/C to allow legacy apps
to do mass updates/deletes for some time without breaking JBoss,
finally switching back to A when the other app is done. Do you
see a chance to have that?
Thanks for your time
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
PS: I know, I just should do that in an Open Source project.
If I get some hints, I might volunteer. May be, via the
JMX management interface it could be done already?
> now I will have to change the training
Is this training available?
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development