Jörn Nettingsmeier wrote: [...]
> would it be possible for the default and blog publications to > fallback-override a usecase view? You can just put the JX template in <pub>/lenya/modules/ac-impl/usecases But I didn't do this because this would be inherited to all instances. > iiuc this ends up in cocoon.xconf, which would mean that the avalon > component resolver would have to > a) understand fallback://, which it might be able to do Hmmm, what do you mean by "component resolver understands fallback"? You don't resolve components by URIs ... > b) not cache the stuff, to be able to do the correct thing for multiple > publications. this is most likely impossible. > > doesn't look too promising. > > what about publication-specific usecases? how does the > <pubname>/<usecase> scheme work? the blog publication uses that, maybe > we could redefine the ac.login usecase in default and blog? That would be possible. I guess it is not even inherited ATM, but IMO it should, and this would again lead to the undesired effect :) -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
