You should add the following lines in your xbean.xml (assuming you use ServiceMix components) <classpath> <location>.</location> </classpath>
Locations are relative to the root of the deployed SU and components will add these locations to the classpath for the SU (used when loading the xbean.xml file). This is the best way to go. Cheers, Guillaume Nodet On 5/11/06, Peter Klotz <[EMAIL PROTECTED]> wrote:
Hi Guillaume, Guillaume Nodet wrote: > Relying on the current dir is not a good idea imho. > You should put your file in the classpath and use the > classpath:backend_local.xml value, unless you refer to absolute dirs Unfortunately when one puts all files in the SU and accesses it using classpath: method, the files itself are way down in wdir/service-assemblies/<hundred subdirs>/.. if it is a file that the installer or even a customer should be able to change this is not a feasable method. A installer wants to install and configure a global configuration file before a SU has been deployed even. In these cases using file:<relative> path is the only way. And it would be good if one could rely on having a relative path to the servicemix home directory in any case. Absolute path names are not really feasable because who writes that absolute path into the servicemix.xml packed into a SU zip in a SA zip? In reality this is not an option. Peter
