You should be able to download the new war from:
http://forge.objectweb.org/nightlybuilds/pres-server/pres-server/2.7.2.200502101403/orbeon.war
(Note that this is a temporary place because the project name on the OW Forge should be changed soon.)
-Erik
Eric van der Vlist wrote:
Le mercredi 09 f�vrier 2005 � 22:59 +0100, Eric van der Vlist a �crit :
Le mercredi 09 f�vrier 2005 � 22:26 +0100, Eric van der Vlist a �crit :
Well, as you say, the code doesn't seem to reach my code. The start() method is called, but the createOutput() one doesn't appear to be called...
There are probably several issues in my sample.
If I add a addOutputInfo(new ProcessorInputOutputInfo("manifest")); instruction in the processor's construct, the createOutput method is called but the start method isn't called any longer.
Ooops, sorry that's working fine with the addOutputInfo (I shouldn't be working that late: the name didn't match the one in the pipe).
To recap, the following is still true:
The fact that in one case the start method is called and in the other case the addOutputInfo method is called makes me suspect that the pipeline processor could miss the fact that there is a connected output when I don't say it in my implementation.
Can it be a side effect of the Java processor?
But this is wrong:
After that, I am wondering why connecting the input to the output simply using SAX doesn't seem to be working...
When the pipeline processors detects that the output is connected, connecting it to the input using SAX does work (the contrary would have been surprising!).
Eric
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
