Re: Problems resolving internal paths

2003-01-03 Thread Timothy Larson
Anybody know a simple equivalent to use in XSL? Tim [EMAIL PROTECTED] 01/02/03 02:30PM If you are using XSP, then you can get the current path with: xsp:exprresolver.resolve().getSystemId()/xsp:expr Or the current path with a filename on the end with:

Re: Problems resolving internal paths

2003-01-02 Thread Timothy Larson
If you are using XSP, then you can get the current path with: xsp:exprresolver.resolve().getSystemId()/xsp:expr Or the current path with a filename on the end with: xsp:exprresolver.resolve(somefile.ext).getSystemId()/xsp:expr Tim [EMAIL PROTECTED] 01/01/03 01:57PM Reinhard Poetz wrote:

RE: Problems resolving internal paths

2003-01-01 Thread Reinhard Poetz
Hi Alexander, Try to use relative paths in your src attributes (your base directory is always the current sitemap) - this should solve your resource not found problems. Regards, Reinhard -Original Message- From: Alexander Czernay [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January

Re: Problems resolving internal paths

2003-01-01 Thread Alexander Czernay
Reinhard Poetz wrote: Hi Alexander, Try to use relative paths in your src attributes (your base directory is always the current sitemap) - this should solve your resource not found problems. Regards, Reinhard Isn't there any way to get absolute paths? I wanted to keep all the needed