What I've been trying to say all along is that you have the expected behavior and you will get
/contextpath/base// rather than /contextpath/base/workspace/collection-name If you don't supply urlFor with values for the route variables. You took care of this when you overrode getHref so there's no issue that I can see. If there's a bug, it's probably in the abstract base and it's more an issue with code obfuscation. I don't particularly like the way getHref was done. Too much indirection. davep On Fri, Aug 1, 2008 at 1:53 AM, James Abley <[EMAIL PROTECTED]> wrote: > 2008/7/31 David Primmer <[EMAIL PROTECTED]>: >> follow this thread for history >> urlFor in RouteManager does not let you null out vars >> http://www.mail-archive.com/[EMAIL PROTECTED]/msg02666.html >> https://issues.apache.org/jira/browse/ABDERA-162 >> >> davep >> > > Thanks Dave. > > I'm actually using TemplateTargetManager rather than RouteManager. I > guess I don't understand named routes well enough to know why this > isn't working and what I'm doing wrong. > > Cheers, > > James >
