Revision 3079 / Ticket 1403 gets wrong webpath when a RootController is not the app's RootController

[Brian Beck]

Hi,

So in 3079 webpath is determined differently:
#webpath = self.__class__.url(webpath)
webpath = PREFIX + webpath

This change assumes that the app has only one RootController.

Having multiple RootControllers in an app is useful if you don't know
where a controller will be mounted in advance and therefore want all
url() calls to determine absolute paths relative to the
RootController.

For example in Pagoda[1] the user's app is a RootController (say
RootControllerA), but the attached administration interface for Pagoda
is *also* a RootController (say RootControllerB) that is mounted
somewhere on RootControllerA. With this change, resources for widgets
used in RootControllerB will 404 because it doesn't use
RootControllerB's url function.

[Alberto Valverde]

Hmm, I'm reopeing that ticket to look into this sometime. I think the
best solution will be to integarte TW into TG 1.1 using middleware
instead of the ugly hack mods.tg is now, that should solve the
webpath issues once and for all and make intergration into 2.0 and
1.1 less divergent. I had some issues when I first tried though but I
guess it's doable...

Thanks for the report,

Alberto