Rami Ojares wrote:
Full acceptance with satisfaction guaranteed.
DelegatingFileSystemOptionsBuilder is our friend.
FileSystemOptions fso = new FileSystemOptions();
DelegatingFileSystemOptionsBuilder delegate = new
DelegatingFileSystemOptionsBuilder(VFS.getManager());
delegate.setConfigString(fs
> But i have to say i dont like to add all those configuration stuff to
> the uri - maybe this might be a handy place, but adding e.g. path
> elements like those in your example might be a real pain. It might be
> really hard to construct a correct uri.
I agree. It was just an example.
> Now
Rami Ojares wrote:
All you have written seems right - hard work ;-)
But if one would tell them for example
sftp://id=/path/to/.private.key;knownHosts=some/[EMAIL PROTECTED]/usr/local/var
then that would just override the providers defaults set from the configuration
file.
But i have to say i don
> Now the configuration (file) can be passed as path, File, FileObject, DOM or
> whatever.
Here the word "Now" does not mean that "now the implementation is ..."
It means "In general it is possible ..."
- rami
-
To unsubscribe
Hi Mario,
Here I have listed my current understanding of VFS in connection with
the configuration issues. Could you please correct any mistakes you find.
- Manager contains FileProviders
- Manager supports all schemas for which it has configured a provider
- FileProviders create a FileSystem the
> I tried to replace the parsing of the xml file by commons-digester &
> beanutils but failed as it comes to the point to add those dependencies
> to vfs. Other people vetoed against it (Too large jars)
That is a shame. But isn't it so that we should first come up with
a configuration structure
Mario Ivankovits wrote on Wednesday, June 23, 2004 9:48 AM:
> Hello Rami,
>
> here are some thoughts about "configuration":
>
> *) GlobalConfiguration:
> As you have seen, the StandardFileSystemManager currently uses an xml
> file to configure the system. I tried to replace the parsing of the
>
Hello Rami,
here are some thoughts about "configuration":
*) GlobalConfiguration:
As you have seen, the StandardFileSystemManager currently uses an xml
file to configure the system.
I tried to replace the parsing of the xml file by commons-digester &
beanutils but failed as it comes to the point
Here are some small changes that I came across when making the changes compilable.
I changed configure method to init because there was already
private configure(String)
method in DefaultFileSystemManager but the existing init method
was without arguments.
I saw also that there is quite a lot of
