Brian Oxley wrote:
[A quick meta-question: is this list the right place for technical questions of this sort? I don't want to spam the uninterested.]I've been thinking about extending java.io.File to implement vfs-alike functionality. Are there any good reasons not to do this (other then that commons-vfs is already available)? Having a subclass of java.io.File would allow you to use your objects with 3rd party components and other java classes that work with files too.
Mario Ivankovits wrote:
Before I decide to make it public (and non final) could you please explain in short what you try to do?
I'm working to persuade my group to drop an inhouse implementation of a java.io.File-extended hierarchy and switch to VFS's FileName/FileObject instead. We have a mess; you have a clean design.
How impossible would it be to have java.io.File subclasses as wrappers around vfs?
Just some random thoughts. Regards, Matthijs
PS. I hope this answers your meta-question :)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
