interceptor-element?
Ted Husted wrote:
On 7/24/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
Guessing how busy you are, you may not be interested, but I think it's
pretty
obvious that the more user-friendly a name is, the more it will be
used by the
community.
Interceptor-ref probably describes exactly what it is in framework
architecture
terms, but something like 'goal', 'phase', 'execution' or 'command' will
undoubtedly be alot better received. (I grabbed those from the maven
vocab, in
case you didn't notice).
The obvious name is interceptor-stack, but the DTD uses that for
another purpose. The interceptor-ref can be a single interceptor,
another interceptor-ref, or any combination of the two (e.g., a
composite). It's role in the framework is to create what Struts 1
calls the "request processor" or "controller". In Struts 1.3, the
request processor is a chain of commands, and, so, conceptually very
close to an interceptor stack.
A syntatically sweet name might be "controller", but since it's
implemented as a composite of interceptor stack, that name would mask
what it is doing, and probably make it harder to use.
<interceptor-stack-composite> might be the most descriptive, but it's
a lot to type, and the DTD is designed to be keyboard friendly.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Java Web Parts -
http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
