Hello Peter, I would suggest you use the current Version from CVS or the snapshot builds. This would have the big advantage that you can actually test and contribute to this version in case you miss some features or find some bugs.
If you want to implement your own file system provider, you typically start to copy one of the existing providers and adopt it. The main work is one in Implementing a specific FileObject which extends from AbstractFileSystemObject and implements all the various doSomething() methods. Actually the JavaDoc of that Abstract Object is quite good in this regard. After you have implemented the new Filesystem, it will be available for addProvider() or you can add it as a new provider to the xml configuration of StandardFileSystemManager like described here: http://commons.apache.org/proper/commons-vfs/api.html Greetings Bernd Am Sun, 27 Jul 2014 15:24:57 +0530 schrieb Richards Peter <hbkricha...@gmail.com>: > Hi, > > I am evaluating commons-vfs 2.0 for one of my use cases. I read that > commons--vfs 2.1 has a file system implementation for HDFS. Since > commons-vfs 2.1 is still in development and commons-vfs 2.1 does not > have all capabilities that we require for hdfs, I would like to > implement a custom file system with commons vfs 2.0 now and enchance > commons-vfs 2.1 when that release is made. > > Could you please tell me how to implement a such a file system for > commons-vfs 2.0? I would like to know: > 1. The specific classes that need to be implemented. > 2. How to register/supply these classes so that it can be used by my > application? > 3. How the name resolution takes place when I provide a filepath of > hdfs file? > > Thanks, > Richards Peter. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
