This is because what follows the "oxf.servlet.input." parameter name is the actual name of the processor input to connect. The WAC takes one "controller" input, hence the name is "oxf.servlet.input.controller". A pipeline takes a "config" input, so the name must be "oxf.servlet.input.config".
You are not limited to specify one input. If you pipeline has another input called for example "properties", you can connect it using the name "oxf.servlet.input.properties".
-Erik
Hank Ratzesberger wrote:
> I have some more information and questions on this.
>
> If I specify the pipeline processor in my properties.xml:
>
> <property type="string" name="oxf.servlet.processor" value="oxf/processor/pipeline"/>
> <property type="string" name="oxf.servlet.input.controller" value="oxf:/config/controller.xml"/>
>
> I get the exception:
>
> org.orbeon.oxf.common.ValidationException: Cannot find input "config"
> at org.orbeon.oxf.processor.ProcessorImpl.getInputByName(ProcessorImpl.java:88)
> at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:445)
> ....
>
> When I attempt to use the webapp-controller processor in the properties
> file and the identity processor in the xpl file, it works.
>
> For now, I would like to use the pipeline processor, but, if I specify it
> in the properties file, I get the exception above.
>
> Is there an example that doesn't use the webapp-controller?
>
> --Thanks,
> Hank
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
