What worked in our case was to simply try the delete more than once. It didn't even seem to matter if there was a delay between the two retries.
--
Jess
On 8/31/05, Gili <[EMAIL PROTECTED]> wrote:
You might want to revisit some of the classes in this package. I might
understand Duration which is a immutable Date object, at least you're
gaining something tangible there. But what is actually gained by
wicket.util.Task when Java already has Timer and TimerTask which do the
same thing? Also Files.remove(File file) looks like a hack at best. I
followed the URL mentioned in the method and it looks to me like these
people were on crack or something. There is no problem deleting files
under Windows. My application does this on a regular basis. If you read
the 2nd to last comment on the first page (by tommyxman1) you will
notice that he was forgetting to close a FileInputStream, and I suspect
similar problems are responsible for the rest of the posters' problems.
Our hack seems to encourage a finalizer to run but the correct behavior
is to properly close the file in the first place. Anyway, you might want
to drop some of these classes and begin using the built-in Java equivilents.
Some of the classes in wicket.util have a good usage (they provide
helper functions around preexisting Java classes) but others such as
Task simply reinvent the wheel with no obvious benefit.
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
