>> I've been following this discussion for the last week or so and suddenly >> this morning I had to start questioning exactly what the true purpose of all >> this is? The idea of being able to dig out a value based on a precedence >> hierarchy makes sense, but XML and XSLT already have very good mechanisms >> for doing this (and Cocoon provides perfectly adequate ways of building XML >> and running XSLT!). Consider, for instance: > > You are absolutely right. It's just that these InputModules serve the purpose > of returning small values, and that often multiple times from the same source. > The DatabaseActions make use of this heavily. I wouldn't want to use pipelines > for obtaining 30 values through the use of the request generator and some xslt > resulting in 30 executions of this pipeline.
I guess, that's part of the problem I have with this: I'm much more comfortable with producing XML directly as database output and using it directly in XSLT than I am in using the half procedural half functional XSP model (though perhaps you're using this some other way?). If you have an XML dataset and XSLT processing you usually don't need to reference a value multiple times (you use XSL keys, parameters or variables if you do). If you aggregate all your XML sources you don't need multiple processing steps (except as desired to separate business logic from presentation logic). So, once more I'm still wondering about exactly what the conceptual problem is that all of this is really supposed to solve? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
