Orbeon Team and all,
In the "controller" section of my application's flow I interleave
between using pipelines and page-flow controllers. The reason I'm
doing this is because my application supports methods other than GET
and POST and I'm using the request-generator to determine what
page-flow to run. [1]
The problem is this: In the case of a PUT (and this general problem
appears in other places) I have to generate the request info to
determine what path my application needs to take, and then again later
on to get the body of the request.
I'm trying to keep my application as DRY[2] as possible, so rather
than have to call the generator twice, I would prefer to generate this
information somewhere near the beginning and pass it down through the
various pipelines and page-flows till it's needed again.
I tried adding another input to my page-flow processor and then had a
pipeline declared as a view. In that view, I declared an input with
the same name as what I passed to the PFC. Not too terribly
surprisingly, I got the error: Pipeline input "request" is not
connected
Is there any way to make a document generated in one pipeline
available to another pipeline despite the fact that the flow goes
through a PFC? I suppose I could always forgo the second PFC processor
and just choose/when based off the query, but seeing as the PFC was
made for this very purpose, I'd really hate to re-invent the wheel.
(octagonal seems like a good shape to me :) )
[1]:
http://mail-archive.objectweb.org/ops-users/2007-03/msg00199.html[2]:
http://en.wikipedia.org/wiki/Don't_repeat_yourself--
Daniel E. Renfer
http://kronkltd.net/--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Locked
