Unico Hommes wrote:
I mentioned this before but never managed to decide on what should happen with it. The "Using Sources" core samples require XSP to be present. Since XSP moved to a block recently there remains this unresolved dependency of the core on XSP block. What to do?
1. Leave them there, provide a notice (there are some other places in the core
samples that do this)
+1
2. Move the samples into the XSP block (probably requires the most work and
raises the question under what heading to place them)
-0.1: Sources, as concept, should be well explained in the core, as it is core concept.
3. Zap them samples completely
-1
I personally tend to option 1 although such ubiquitous use of XSP in a core
concept such as Sources may give the impression of XSP as an endorsed best
practice for Cocoon.
What would you use instead? jx stuff is too buggy, and we don't have other server pages technology beside xsp.
Vadim
