You might want to check this Calvin. We have exchanged a few messages in private since last Friday and Calvin found out that the source of the problem was a missing input in a dynamically generated pipeline (generated with XSL).
This would have normally not have been a big deal; the Pipeline processor would have signaled the error. And indeed, an exception was thrown by the Pipeline processor but it was "eaten" by a custom processor in the application. Unfortunately, after an exception is thrown by OXF, the execution must be aborted as the internal state stored in the PipelineContext becomes invalid.
A "no state in context" exception is an internal error. It is thrown as we check the consistency of the state stored in the PipelineContext. So you should never see this message. If you do, it means that either one of your custom processor is doing something forbidden (like "eating" exceptions in this case), or that there is a bug in OXF.
Alex
Justin Makeig wrote:
I was having this error intermittently this weekend as well. I'll try to reproduce it.
- Justin Makeig
-- Center for Document Engineering University of California, Berkeley
On 8/22/03 7:28 PM, "Alessandro Vernet" <[EMAIL PROTECTED]> wrote:
Calvin Smith wrote:
It is reproducible. I'll package up a war file and post in on the web, but we may have the same troubles we had last week when you were trying to run our war file. I'll send details shortly.
Ok, great, I will have a look at it and keep up updated.
Alex
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
