That was my thought originally, but when while writing a rule that
utilizes the information, the API "felt" awkward; if I care about the
page name, for example, do I really care about whether this is a
component event or a page link, if what I'm after is the page name?
But after debating this for awhile, I opted to leave this "as is".
Robert
On Apr 9, 2009, at 4/97:36 PM , Howard Lewis Ship wrote:
Given that ComponentEventRequestParameters and
PageRenderRequestParameters are immutable, what's the pain of exposing
them?
On Thu, Apr 9, 2009 at 4:01 PM, Robert Zeigler <[email protected]>
wrote:
Committed changes for distinguishing incoming/outgoing requests for
url
rewriting (tap5-612). I'm not sold on some of the names
(RewriteRuleApplicability, for example, is a bit unwieldly, IMO...
but I
couldn't think of anything better). Also have mixed thoughts about
exposing
ComponentEventRequestParameters and PageRenderRequestParameters via
the
URLRewriteContext object. I wonder if perhaps I should provide
facade
methods, instead: getPageName, getComponentId, etc. But it's a step
in the
right direction. Feedback appreciated.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
