[ http://issues.apache.org/jira/browse/VFS-82?page=comments#action_12437969 ] Ethan Killian commented on VFS-82: ----------------------------------
In addition to the original delete issue with ClassCastException on a DecoratorFileObject there are additional issues with renames. I have only looked at the Local provider and there may be additional issues in all of the other types of providers since for the rename it was an issue with the LocalFile. I have included an updated patch for AbstractFileObject and included a patch for LocalFile. > ClassCastException in AbstractFileObject when using OnCall caching > ------------------------------------------------------------------ > > Key: VFS-82 > URL: http://issues.apache.org/jira/browse/VFS-82 > Project: Commons VFS > Issue Type: Bug > Affects Versions: Nightly Builds > Environment: Windows XP > Reporter: Ethan Killian > Attachments: AbstractFileObject.patch, AbstractFileObject.patch, > LocalFile.patch > > > When using OnCall caching in the file system, there is a ClassCastException > in the AbstractFileObject because it assumes that every child it will > encounter will also be an AbstractFileObject as well. > Here is the stack trace in question: > Exception in thread "AWT-EventQueue-0" java.lang.ClassCastException: > org.apache.commons.vfs.cache.OnCallRefreshFileObject > at > org.apache.commons.vfs.provider.AbstractFileObject.delete(AbstractFileObject.java:748) > at > org.apache.commons.vfs.impl.DecoratedFileObject.delete(DecoratedFileObject.java:79) > at > org.apache.commons.vfs.cache.OnCallRefreshFileObject.delete(OnCallRefreshFileObject.java:74) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
