One nice thing about Struts and Spring is that *everyone* knows how to
start examining and working on the application.
Just go to the config.xml!
It tells you where to start and what gets called and I can open it and
start there. Once you get rid of a config .xml, there is no guide to the
application, I have to look at packages and code, etc. and I have at
times re-written things because it was faster than trying to figure out
what they guy before me did. A guide that requires documentation.
2ndorily, CoR is a huge feature, developing a library of reusable
"action brick" that can be mixed and matched. So you can use them in
other configurations an contexts. Plus digester type features to ...
"inject". Like to use the commands w/ WS, etc.
-1
.V
Craig McClanahan wrote:
On 12/23/05, David Geary <[EMAIL PROTECTED]> wrote:
I don't understand the requirement that remote calls must be
made
to Commons Chain commands.
instead invoked methods on managed beans using
reflection. Sort of a remote value binding.
All we probably need is a mechanism to map a request URL pattern to a
particular method on a particular bean ... and this might be a place where
all of the mechanisms (conventional configuration files, annotated service
classes, and/or convention over configuration techniques) might have a role.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
