Not according to the code, they're not. Check out AbstractProcessingPipeline.java. There are method bodies like:
public void setGenerator (String role, String source, Parameters param, Parameters hintParam)
throws ProcessingException {
if (this.generator != null) {
throw new ProcessingException ("Generator already set. You can only select one Generator (" + role + ")");
}
if (this.reader != null) {
throw new ProcessingException ("Reader already set. You cannot use a reader and a generator for one pipeline.");
}
...
and
public void setReader (String role, String source, Parameters param, String mimeType)
throws ProcessingException {
if (this.reader != null) {
throw new ProcessingException ("Reader already set. You can only select one Reader (" + role + ")");
}
if (this.generator != null) {
throw new ProcessingException ("Generator already set. You cannot use a reader and a generator for one pipeline.");
}
...
Either the policy was in effect when this file (and its subclasses) were made or someone put constraining statements in that serve no purpose. The file was last modified on August 6th of this year. If the policy has changed, no one told the code.
This has been there for a very long time. And has nothing to do with the fact that readers and serializers end the execution of the sitemap : check ReadNode and SerializeNode in o.a.c.components.treeprocessor.sitemap.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
