commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank van der Kleij <kl...@hotmail.com>
Subject RE: [VFS] How to use operations
Date Mon, 14 Jul 2008 11:13:35 GMT

Ah, now I see! Sorry, I tried to refer to the 'FileOperations': FileObject.getOperations().

There is some code in org.apache.commons.vfs.operations and org.apache.commons.vfs.operations.vcs.

Thanks for helping me clarify.

Frank

> Date: Mon, 14 Jul 2008 06:38:25 -0400
> From: james@carmanconsulting.com
> To: user@commons.apache.org
> Subject: Re: [VFS] How to use operations
> 
> What I'm getting at is that if you stick to the VFS public API (the
> FileObject interface), you should have a pretty good idea of what
> operations are available across the different implementations.  Of
> course, some implementations don't support all operations (HTTP can't
> give you a directory listing for instance).
> 
> 
> On Mon, Jul 14, 2008 at 5:41 AM, Frank van der Kleij <kleij@hotmail.com> wrote:
> >
> > Yes, I guess so; are there other APIs? I don't see where you getting at...
> >
> > Thanks,
> >
> > Frank
> >
> >> Date: Sun, 13 Jul 2008 21:37:26 -0400
> >> From: james@carmanconsulting.com
> >> To: user@commons.apache.org
> >> Subject: Re: [VFS] How to use operations
> >>
> >> Are you sticking to the FileObject API?
> >>
> >> On Sun, Jul 13, 2008 at 2:41 PM, Frank van der Kleij <kleij@hotmail.com>
wrote:
> >> >
> >> > Hi all,
> >> >
> >> > I'm toying with my own VFS operations but I can't quite figure out how
to work with them.
> >> >
> >> > I
> >> > don't see how a client of the VFS framework should use the operations;
> >> > other than when the client has prior knowledge of the operations that
> >> > exist.
> >> >
> >> > I wrote a beanshell script that rewrites the basic
> >> > beanshell interpreter file manipulations (cd, pwd, cp, mv etc) to VFS
> >> > manipulations. It works  great and  I can use my custom provider (for
> >> > Documentum) without any problem within the beanshell interpreter. When
> >> > I tried to add support for operations I found that it is difficult to
> >> > make  it generic though.
> >> >
> >> > I added some operations to my provider
> >> > just to try; when I list the available operations I get a list of
> >> > Classes. As a user it is quite hard to interpret this. I could try to
> >> > use Reflection, but a user readable description of what the operation
> >> > seems far away.
> >> >
> >> > In my view the operations only become
> >> > interesting when they are usable by a generic VFS client. If the client
> >> > is specific for the operations (I guess most operations are related to
> >> > a provider for a particular schema)  then I don't see the need to have
> >> > the intermediate VFS layer, you can as well  create a client based
> >> > directly on the underlying layer.
> >> >
> >> > Does anyone have any experience with using the operations?
> >> >
> >> > Thanks,
> >> >
> >> > Frank
> >> > _________________________________________________________________
> >> > Express yourself instantly with MSN Messenger! Download today it's FREE!
> >> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: user-help@commons.apache.org
> >>
> >
> > _________________________________________________________________
> > Express yourself instantly with MSN Messenger! Download today it's FREE!
> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
> 

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message