Good day, Mario. +1 vote from me. This is very common case, when deleveloper allows user to specify URI only.
More over, this setting is file-specific (or, more precisely, site specific), so it's not always correct to set them up using ConfigurationBuilder. Another example is to add "classloader" parameter to ResourceFileSystem's URIs, which specifies classloader to use: "thread" for current thread one, "vfs" for ResourceFileSystem.class.getClassLoader() or "system" for system class loader. -- Bets regards, Sergey. 2007/8/29, Asankha C. Perera <[EMAIL PROTECTED]>: > > Hi Mario > > > It is possible through the *FileSystemConfigurationBuilder stuff only. > > > Unfortunately this does not work for me, as I can only specify a VFS > URI. So VFS needs to figure out and make it happen in my case > >> > ftp://myusername:[EMAIL PROTECTED]/pub/downloads/somefile.tgz?option=value > >> > >> > >> Have I missed something to get passive mode specified via the URI or > >> can we assume the above to be a good solution? > >> > > > > I don't think that adding them as option to the URI is a good idea as > > the URI parameters are meant to be processed by the destination (e.g. an > > http server) and not by VFS. > > > I don't quite agree with this - this may be the common case for HTTP, > but the URI spec does not enforce it. > / > /_http://www.w3.org/Addressing/URL/4_URI_Recommentations.html:_/ > "The query string represents some operation applied to the object, but > this specification gives no common syntax or semantics for it. In > practice the syntax and sematics may depend on the scheme and may even > on the base URI."/ > > Also there are IRI schemes that specify such parameters already. Ref the > JMS scheme here > < > http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200701.mbox/raw/[EMAIL > PROTECTED]/2 > > > > thanks > asankha > -- Sergey Vladimirov
