Martin,
You have two scenarios:
1. An output is read. In that case, createOutput() is called, and start() is not called.
2. No output is read. In that case, start() is called.
Now this behavior may be broken in the case of the Java processor. What happens if you put a debug statement on the output connected to the File serializer, or if you replace the File serializer with the Null serializer?
-Erik
Martin Schulte wrote:
Hi,
I've a class here that extends ProcessorImpl.
It has a no-arg constructor, a
public void start( PipelineContext pipelineContext ),
and a public ProcessorOutput createOutput( final String name ).
When I call it from my pipeline (I use oxf:java at the moment), I see logging statements that start is invoked and but I don't see that createOutput is invoked. There's an used output (connected to the file serializer) and this file serializer gets an null pointer exeception.
Am I misinterpreting createOutput?
Greetings,
Martin
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
