Andreas Hartmann wrote:
Jürgen Ragaller wrote:
... got my xslt together!
A followup question: In the java comment of the
PageEnvelopeModule.java it says:
@deprecated use DocumentInfoModule instead.
I have plenty of {page-envelope:bar} variables in the sitemap... I
guess I should rather use the DocumentInfoModule variables if available?
Yes, but this is not a pressing issue.
The page envelope module is especially error-prone when used in modules
(commonly used pipelines).
If you're interested in the reasons, you might want to search the dev list.
the short answer is that: using {page-envelope:*} is very concise and
neat *as long as you're dealing with the currently requested document only*.
so if you write your own resource type, you can use it to handle user
requests.
the pain starts when you want to make your custom resources available
for searching: when the indexer is called, the currently requested page
might be something else, like /index (and you should not make
assumptions about that anyway).
so when you want to implement a "luceneIndex" match to prepare your
content for indexing, you need absolute addressing, independent of the
page envelope.
see
src/modules/xhtml/config/cocoon-xconf/resource-type-xhtml.xconf and the
xhtml sitemap for how it can be done.
andreas, we really need more detailed info about this in the "custom
doctypes" documentation. i think i can say that i've been digging around
quite a bit in lenya lately. still i totally failed to notice that
DocumentInfoModule exists...
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
