Holger, Thanks for the amazingly helpful response. We now have enough information to get our app running.
At least this email thread will help other people understand what is going on if they run into this issue. Cheers Duncan 2011/4/29 Holger Hoffstätte <holger.hoffstae...@googlemail.com>: > On 29.04.2011 17:30, Richard S. Hall wrote: >>> In that case the only way out is to first try $ORIGIN and, failing that, >>> a fixed location like /tmp or any other directory to which your bundle >>> can unpack the libraries and try again. It's much more difficult to get >>> right since you really want to clean up afterwards, not clash with other >>> instances of your bundle on the same machine (need a cooperative locking >>> mechanism) etc. >> >> Could you do it in the bundle's private data area? > > In theory yes, but: > > - I'd have to know that location in advance (unless I do the crazy > on-demand patching) > > - the fullly expanded path must not be longer than (I think) 14 characters > > ..so in practice probably not. > > "It's complicated". :D > > -h > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
