Re: Spring: confusing application context with change working directory

[Guillaume Nodet]

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
...

Cheers,
Guillaume Nodet

On 5/10/06, Peter Klotz <[EMAIL PROTECTED]> wrote:

Hi,

I have a strange behaviour with the Spring as it is build into SM.
I have multiple SA deployed (lwcontainer) and use the Spring resource loading

e.g.

<property name="localBackendResource" value="file:conf/backend_local.xml"/>

When there is a component that changes the current working directory, as is
obviously a Jetty 6 in embedded web application mode then for all following
components get their files specified like so above, resolved to the new current
working directory. As I do not have an influence on components change working
directory behaviour, this is somehow not ok.

e.g. Jetty 6 changes obviously the working directory to webapps/<webapp>

---
                       <exception-info>
                                <nesting-level>1</nesting-level>
                                <msg-loc-info>
                                        <loc-token/>

<loc-message>java.io.FileNotFoundException:
/public/Temp/pak/midas/webapps/exist/conf/backend_local.xml (No such file or
directory)</loc-message>

<stack-trace><![CDATA[javax.jbi.JBIException: java.io.FileNotFoundException:
/public/Temp/pak/midas/webapps/exist/conf/backend_local.xml (No such file or
directory)
---

when my jetty SA is not deployed everything works fine.

IMHO, servicemix should for each service-unit at least make sure that the
current working directory is set as was when servicemix was started. Otherwise
this behaviour highly depends on what components get loaded or in which order.
Would this be possible?


Thanks, Peter