El mié, 18-01-2006 a las 21:17 -0500, Doug Chestnut escribió: > Hi Felix, > I have just started to see this problem as well. A request for > fallback://xslt/page2xhtml.xsl seems to get cached, and is used by other > publications. Odd that I haven't seen it till now. Have you found a > solution? >
I have not a simple solution but maybe it makes sense to use the locationmap http://forrest.apache.org/docs_0_80/locationmap.html instead of the fallback. The argumentation why is that you can a) do the same as with the fallback source b) do much more and you are much more flexible in doing it >From above linked document: "A locationmap defines a mapping from requests to location strings. It was conceived to: * Provide a more powerful means for semantic linking. * Enable Forrest with a standard configuration override mechanism. * Decouple the conceptual source space used by Cocoon from the concrete source space, so that a change in the concrete sources does not impact on the sitemap. In other words, the locationmap enables content to be retrieved from a location that is defined in a locationmap file (located at PROJECT_HOME/src/documentation/content/locationmap.xml file. The advantage of this is that the URL seen by the user need bear no relation to the location of the source document, thus Forrest can separate the client URL space from the source document URL space. Thus, using the locationmap it is possible to pull together documents from many different locations into a single uniform site." I would be happy to help seeting the locationmap up for lenya if you need help, but IMO it is worth considering. The good news about it is that lenya-trunk has a forrest.jar, so you can set it up nearly like described in above link. A while ago I added a pseudo source protocol (lm://) to access the locationmap, so it is not anymore only an input module. wdyt? salu2 > Thanks, > --Doug > > Felix Röthenbacher wrote: > > Hi > > > > I wonder how the fallback: protocol behaves when it comes > > to caching? If several publications are in use at the same > > time and resources are accessed with the fallback: protocol, > > it seems that a cached resource is used instead of the resource > > which applies to the current publication. Has anyone else > > seen this behaviour? > > > > Thanks for sharing your thoughts, > > > > - Felix > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
