Hi Matt,
In general I totally agree with you about docs. However, given that every
area is built the same (controller, model and view in the same dir), and
that we know we're playing MVC so the concepts are very familiar, I thought
these kinds of hookups could be 'magic' without it being a problem.
Except for the pattern-matching goo that'd have to be in ColdSpring to
actually do it, that is (;-)
The way we handle this currently (no ColdSpring) is a method in the base
class for all controllers; you pass in your object's 'root name' ('User'),
and it assumes the registered names of your model and view are based off
that. It works fine, but my dislike of it is one of the things that led me
to look at ColdSpring in the first place.
Dave Merrill
> On 9/4/06, Dave Merrill <[EMAIL PROTECTED]> wrote:
> > So does everyone hand code all these MVC relationships?
> >
>
> I can't speak for everyone, but yes. I hand code all beans in my CS
> config file. I guess one argument for doing so is documentation. In
> fact I only rely on autowiring for the controllers/listeners (MachII)
> and explicity define <property> tags whenever a bean is to be
> injected. This way, you can tell a lot about what is going on by
> reading the xml.
>
> --
> Matt Williams
> "It's the question that drives us."
