Hi,
I would like to customize the way Tapestry handles responses from
EventHandler methods.
Basically what I want to realize can be summarized like this:
- If the request contains a special "flag" attribute that I set then
Tapestry have to manage the results as I decide
- If the request does not contains the flag attribute, then Tapestry
have to manage the results as usual
My hope was to contribute to some services such that I can put my own
ComponentEventResultProcessor service in front of all the others (like
a wrapper or a filter).
unfortunately, the contribution to ComponentEventResultProcessor is a
Mapped contribution and not an OrderedContribution.
And I did not find a smart way to trigger a
DefaultComponentResultProcessor before any other
(BWT, ObjectEventResultProcessor is the fall back one but I do not
know if it is called before or after the others as it is supposed to
match all the Objects).
In the meanwhile, I workarounded this problem by overriding each of
the basic EventResultProcessors with a wrapped version. This solution
is working, but it is not the cleanest one, in fact
it assumes that there's no other contributions to the original set of
ResultProcessors, and there's a lot of duplicated functionalities.
Moreover, I know that all the requests will be Ajax request so I
started by contributing the AjaxComponentEventResultProcessor.
Unfortunately, I was not able to understand why in most of the cases
the one actually called is the "original" (@Traditional marked)
ComponentEventResultProcessor.
Has anyone an idea on one to realize this customization in a way that
is general and cleaner than the one I designed ?
Will be enough to override the original ObjectResultProcessors to
handle all the kinds of result ?
Thanks
-- Alessio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
