-
1. Re: Dirty data -- the bean is not always king
marc.fleury Sep 11, 2002 3:51 PM (in response to kellymac)you want to use option B for reload or D for time expiration of the cache
-
2. Re: Dirty data -- the bean is not always king
kellymac Sep 16, 2002 11:26 AM (in response to kellymac)Thanks for the reply!
We tried to do this but were not successful. I am sure it is documented but it would be so helpful if you could explain exactly how to make this change.
Thank you,
KellyMac -
3. Re: Dirty data -- the bean is not always king
kellymac Sep 16, 2002 11:29 AM (in response to kellymac)Thanks for the reply!
We tried to do this but were not successful. I am sure it is documented but it would be so helpful if you could explain exactly how to make this change.
Thank you,
KellyMac -
4. Re: Dirty data -- the bean is not always king
juha Sep 16, 2002 8:22 PM (in response to kellymac)conf/standardjboss.xml
-
5. Re: Dirty data -- the bean is not always king
kellymac Sep 17, 2002 11:11 AM (in response to kellymac)Well,
I got it working. I made entries in my project’s jboss.xml file. I added container configuration entries for each of the standard container configurations that were not already set to ‘B’ in standardjboss.xml.
My entries just have the commit-option tag. When you are not specifying a container it is not always clear which one jboss is using so I just changed them all. Do you see a problem with this approach?
Thanks again for your help, Things seem much better now.
KellyMac