Worked, I believe. The failure didn't happen always with every file I tried to edit, so I can't be certain, but it appears to be fixed.
Dave Merrill On Saturday, January 26, 2013 3:02:49 PM UTC-5, [email protected] wrote: > > Nevermind, found it, unjarred in etc. now to see if this fix works... > > Dave > > On Saturday, January 26, 2013 2:50:47 PM UTC-5, [email protected] wrote: >> >> Having this same issue, very annoying. >> >> Additoinally, the file mentioned in the linked article doesn't exist in >> my install of BlueDragon 2.0.2: >> lib/jetty.jar >> >> There are many jetty-related jars in lib, would rather not crack each of >> them looking for org/mortbay/jetty/webapp/webdefault.xml. >> >> Any thoughts? Ideally this would get fixed in the released version, since >> I doubt most people like this behavior. >> >> Dave >> >> On Thursday, August 23, 2012 12:25:09 PM UTC-4, Randy Johnson wrote: >>> >>> I tried to update a css file that was locked today and I found this: >>> >>> >>> >>> http://docs.codehaus.org/display/JETTY/Files+locked+on+Windows >>> >>> >>> >>> >>> >>> Two options are available: >>> >>> >>> >>> 1. Disable memory mapped files >>> >>> 2. Do a web app directory copy on deployment >>> >>> >>> >>> My question is: Does anyone know if there would be any performance hits >>> when disabling memory mapped files? >>> >>> >>> >>> It is not a super big issue for me on a production machine but would be >>> an inconvenience if I had to make a minor update on a file. >>> >>> >>> >>> Randy >>> >>> >>> >> -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en
