>
>
>> The main problem with using ../ here (and other places) is that when the
>> configuration as specified on the command line changes, this breaks.
>>
>
> hu? 



In most places where relative paths are prefixed with a base, the base 
value is determined from ServerConfig.getServerHomeDir(), which is 
jboss/server/<config>/.  

When the --net-boot flag is NOT used, ServerHomeURL  is set to 
ServerHomeDir.toURL(), when it IS used, then ServerHomeURL is set to the 
argument specified.

The server will always have a reference to a file system as set by 
HomeDir and ServerHomeDir.  Components which *must* work from a local 
file system use these values.  Components which can use a URL will use 
the URL versions.

>
> explicit can be good too.  Do you think it is simpler? 


Yes, by far.

It will also make it clearer to users/admins who are configuration 
components to know exactly what the server will resolve the path to 
rather than trial/error/guessing what ../ will turn into.

This seems like a good thing todo on all fronts.  For simplification of 
components that deal with them (they don't have to deal with making 
absolutes), for configuration file clarity and for consistency with 
command line (or embeded) configuration paramers.

And to top it all off... it is simple to implement.

--jason



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to