Hey Chris, Cameron,

So yeah, did figure out a solution. Here it is:

Below is a working Windows example entry for specifying the filemgr policy 
directory within filemgr.properties
org.apache.oodt.cas.filemgr.repositorymgr.dirs=file:///C:/proteome/proteome-filemgr-win/policy

In summary, the key seems to be to specify Windows directory paths using a 
single "/" character to separate directories. Additionally, if the path has 
spaces within it, you should put a "%20" in place of the space within the path.

For more information on how to set Windows-style paths that are interpretable 
by Java, see:
http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx

Thanks for the tips everyone!
rishi

On Sep 6, 2011, at 4:51 PM, Mattmann, Chris A (388J) wrote:

> Hey Rishi,
> 
> On Sep 2, 2011, at 4:45 PM, Verma, Rishi (317I) wrote:
> 
>> Hello fellow developers,
>> 
>> I'm trying to deploy CAS-Filemanager (0.4-SNAPSHOT) to a Windows XP machine, 
>> but am witnessing some warnings due to paths being set for a windows 
>> environment.
>> 
>> Two questions I want to ask:
>> [1] Does filemgr.properties ASSUME a UNIX-like path for the following two 
>> props (org.apache.oodt.cas.filemgr.repositorymgr.dirs, 
>> org.apache.oodt.cas.filemgr.validation.dirs)?
> 
> Nope it assumes #2 below for those props.
> 
>> [2] Is the prefix "file://" for the above two properties applicable only to 
>> a unix environment?
>> 
>> I say this because I have tried (on the Windows machine) to place paths 
>> using Windows-style forward-slash "\" paths, as well as using Cygwin style 
>> paths to the same corresponding directories; however, neither method 
>> eliminates the below warnings when attempting to start filemgr within 
>> Windows (running within Cygwin I might add).
> 
> You got this working, right? Let me know if I understood that correctly 
> and/or if you are still having the problem.
> 
> Thanks!
> 
> Cheers,
> Chris
> 
>> 
>> Thanks!
>> Rishi
>> 
>> ---
>> Below is an attempt to start filemgr:
>> 
>> $ ./filemgr start
>> Starting cas file manager: OK
>> Sep 2, 2011 2:47:30 PM org.apache.oodt.cas.filemgr.system.XmlRpcFileManager 
>> load
>> Configuration
>> INFO: Loading File Manager Configuration Properties from: 
>> [../etc/filemgr.proper
>> ties]
>> Sep 2, 2011 2:47:30 PM 
>> org.apache.oodt.cas.filemgr.validation.XMLValidationLayer
>> loadElements
>> WARNING: Element directory: 
>> file:///cygdrive/c/proteome/proteome-filemgr-win/pol
>> icy is not a directory: skipping element loading from it.
>> Sep 2, 2011 2:47:30 PM 
>> org.apache.oodt.cas.filemgr.validation.XMLValidationLayer
>> loadProductTypeMap
>> WARNING: Element directory: 
>> file:///cygdrive/c/proteome/proteome-filemgr-win/pol
>> icy is not a directory: skipping product type element map loading from it.
>> Sep 2, 2011 2:47:31 PM 
>> org.apache.oodt.cas.filemgr.repository.XMLRepositoryManag
>> er loadProductTypes
>> WARNING: Product type directory: 
>> file:///cygdrive/c/proteome/proteome-filemgr-wi
>> n/policy is not a directory: skipping product type loading from it.
>> Sep 2, 2011 2:47:31 PM 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClien
>> t <init>
>> INFO: Loading File Manager Configuration Properties from: 
>> [../etc/filemgr.proper
>> ties]
>> Sep 2, 2011 2:47:31 PM 
>> org.apache.oodt.cas.filemgr.datatransfer.LocalDataTransfe
>> rer setFileManagerUrl
>> INFO: Local Data Transfer to: [http://localhost:9000] enabled
>> Sep 2, 2011 2:47:31 PM org.apache.oodt.cas.filemgr.system.XmlRpcFileManager 
>> <ini
>> t>
>> INFO: File Manager started
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: [email protected]
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 

Reply via email to