On Thu, 13 Mar 2003 15:54, Niclas Hedhman wrote:
> However, one immediate problem in the migration is the FileSystem. Are
> there any recommendations on how the "file system space" is managed? I.e.
> Is it meant to be that each Phoenix server puts all its file into its
> apps/abc-server/ space, even files that the "server user" is to maintain?

essentially thats the idea.

> In the existing solution I have a concept of ProductDir vs ProjectDir,
> where the former is a standard distro, that the user never change, and
> ProjectDir is for the user only, and can be placed at any place on disk
> with a simple pointer to change at startup. Any recommendations regarding
> this?

I would place the resources in the ProductDir in the jar in the directory

SAR-INF/ProductDir

and then access the resources in it via

getBlockContext().getResourceAsStream( "SAR-INF/ProductDir/myfile.txt" );

By default the dirs inside SAR-INF/ are not expanded to the filesystem and 
thus the user will never be able to see/modify them without editing the .sar 
file.

The user modifiable files I would just leave in base directory of the .sar 
archive. These will be expanded to apps/abc-server/ and you can access it via 
either

getBlockContext().getResourceAsStream( "ProjectDir/myfile.txt" );

or

final File baseDir = getBlockContext().getgetBaseDirectory();
final File myFile = new File( baseDir, "ProjectDir/myfile.txt" );

-- 
Cheers,

Peter Donald
-----------------------------------------------
|  If you turn on the light quickly enough,   |
|    you can see what the dark looks like.    |
----------------------------------------------- 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to