Bob MacCallum wrote: > > Hi, > > This might cause some confusion among users without some knowledge of > what's going on under the hood: > > * Go to list view of freshly created, say, biosources with no annotations > > * run the annotation import plugin to annotate them, it completes successfully > > * do not press refresh page button > > * click on an item to see if it has been annotated: you see that it has no > annotations > > * go back to list page and click on the item again and you'll see that it has > actually been annotated (or click refresh button after the plugin has > finished) > > > I managed to duplicate this behaviour, please let me know if you cannot. > > I realise this is all to do with the objects staying in memory in the > webserver, which makes the GUI nice and responsive. The GUI and plugin > executor are separate entities and cannot communicate.
This seems a bit strange. We are not caching anything in our own code from the list view. We only do this when editing an item to catch concurrent modifications. Hibernate has an internal cache to to avoid database hits at every click, but it should be smart enough to notice the update done by the annotation importer and purge it's cache. Unless... 1. There is a bug in Hibernate 2. The annotation importer is running in a different Java virtual machine than the web interface, eg. on a job agent. 3. Something I didn't think of... /Nicklas ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
