The tapestry request processing pipeline is quite complicated and as you get
further down, it becomes less of a "black box" and you must know more of
it's internals ("white box"). There is a great diagram at the bottom of
http://tapestry.apache.org/request-processing.html this page. One thing to
keep in mind is that as you go down the request processing pipeline, objects
can be pushed onto the Environment thread local.
I recommend that you download the tapestry source code and follow the flow
through from the TapestryFilter. If you were to get down to the low level
RenderCommand and PageRenderQueue code, I think you would find that you will
be copy/pasting quite a lot of the internal tapestry code. Keep in mind that
any class in an "internal" package is considered private, should be avoided
and can change between releases.
I'm happier to not involve myself with the internal code, by invoking the
ComponentEventRequestHandler and reading the response into a JSONObject. I
will be able to access the HTML and javascript for an AJAX event without
needing to involve myself with too much of the tapestry internals.
If you'd like to go further, feel free to dive in ;)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-tp5697644p5709831.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
