commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vince Bonfanti (JIRA)" <>
Subject [jira] Updated: (VFS-266) AbstractFileName and AbstractFileObject serialization
Date Mon, 22 Jun 2009 20:25:07 GMT


Vince Bonfanti updated VFS-266:

    Attachment: VFS-abstractfilename-abstractfileobject-serialization.patch

The attached patch resolves this issue. Two things to note about this patch:

 1. This patch includes the fix for VFS-245. 
 2. This patch inlcudes added a convenience method to AbstractFileCache that is not strictly
required to resolve this issue.

All of the test VFS testcases pass, except for the WebDAV testcases. However, I don't believe
the failures I'm seeing are due to these changes, but reflect my inability to get the WebDAV
testing server configured properly.

> AbstractFileName and AbstractFileObject serialization
> -----------------------------------------------------
>                 Key: VFS-266
>                 URL:
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 2.0
>         Environment: Google App Engine Java
>            Reporter: Vince Bonfanti
>             Fix For: 2.0
>         Attachments: VFS-abstractfilename-abstractfileobject-serialization.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> I'm implementing a VFS plug-in that implements a distributed, writeable file system for
Google App Engine (GAE) Java (see for more info). In order for this to
work properly, I need to create a distributed FilesCache implementation using the memcache
API provided by GAE. However, memcache requires that both keys and values must be serializable.
Therefore, to complete my implementation, I need to make AbstractFileName and AbstractFileObject
serializable (because my implementation classes inherit from these).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message