on 8/9/01 10:12 AM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote: > On 8/9/01 11:59 AM, "Jon Stevens" <[EMAIL PROTECTED]> wrote: > >> on 8/9/01 5:13 AM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote: >> >>> We definitely need a solution, but I was thinking of something a little more >>> general for the services. Paths with a leading '/' are treated as absolute >>> paths whereas something without will be treated relative the application >>> root. This won't really affect anything but the general solution of >>> absolute/relative paths should be be resolved in fulcrum at the service >>> level. This require a bit of work in fulcrum. >> >> That won't work because paths currently start with a /template by default >> and will break existing TR.props. Having them be just "template" would be >> even more confusing to people because it wouldn't look like a path. > > I said it would require some work. What we have is confusing, I think people > generally associate a leading '/' with an absolute path and the absence of > leading '/' to be a relative path. Ok, so lets just make it ./ > You are using an URL notation for something that is not an URL, which is not > standard which is bound to confuse people. Maybe then the solution is to change it to be "file://" instead of "absolute:". That won't confuse people. :-) In fact, that is what I'm going to do. > Plus you've hacked off a solution > for one service which satisfies your needs but won't help any of the other > template services. So what works for velocity based apps will not work for > JSP or any other templating service. Correct. I scratched my itches. > Someone is going to see the "absolute:" notation in a TRP file and try with > JSP and than ask why it doesn't work. I guarantee it. A one off solution for > one service using non-standard notation is definitely not the way to go. I'm strongly +0 to an effort to generalize the approach. -jon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
