Joern Nettingsmeier wrote: [...]
You get the path in the site structure (formerly known as document ID) with {doc-info:{pubId}:{area}:{uuid}:{language}:path} I understand that this syntax is quite verbose, but the implicit page envelope syntax caused some problems - you have to be very careful when writing pipelines which can be accessed for arbitrary documents.thanks for the help. can you elaborate on the problems with {page-envelope:*}? i've been using it a lot in module sitemaps, but i have this nagging feeling that i'm going to regret it some day.
The problem with the page envelope is that you assume that a pipeline applies to the currently requested document. This way, you lose the ability to call the pipeline for arbitrary documents. Actually, it violates orthogonality - you put the mechanism of getting the parameter (the document) and the actual functionality in the same place. You should rather use a (reusable) pipeline like a method - by declaring parameters in the method signature, you make it generic.
some sort of "best practice" hints would be cool, maybe pointers to publications or modules that Do It Right(tm) ?
A good example is indexing in the lucene module - the area, uuid etc. are passed to the pipeline, this way you can index arbitrary documents from the same page context. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
