----- Original Message ----- 
From: "Joe Germuska" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, August 06, 2003 5:07 PM
Subject: Re: Module Inheritance Revisited


> Matt:
>
> This does sound like kind of an abuse of modules (if you'll pardon the
term...)

Pardoned - I probably am abusing them :)  Actually so far my approach is
working very well for our project.  Really the only bad thing is copying
resource bundle properties, global-forwards, and global-exceptions, but we
can verify that is done correctly before major milestones and releases.

> Shouldn't all of that structure be a layer separate from Struts?  It
> seems to me as if "knowledge items" should be part of your data
> model, not tangled up in Struts/Controller-View structures.

Yes, the knowledge items are in the model, but each knowledge item has
different properties to display on various screens (view) and different
business rules (controller).

> Further, I would suggest that if you are going to have trouble
> "finding actions after a few days" then maybe you're using actions in
> a very... er, idiomatic way?

Hehe I think you misunderstood me.  We would have problems finding them not
because of naming conventions but rather because the programmers on my team
tend to arrange their code in, to borrow a good phrase, idiomatic ways.
Struts apps have lots of actions, and it's hard to keep them organized in
some sort of intelligible order in a single configuration file.  (Actually,
it's not hard, but we don't quite have mechanisms in place to enforce this
level of discipline... no CMM here yet).

> I think Struts is very flexible, and I think it's great to try to
> make it more so, and I won't even say that it's foolish to hope that
> Struts could be as flexible as to fit your model -- but wooo-eee,
> you're pushing it to the limit!  I'm hearing Mr. Scott... "she canna
> take no more, Cap'n!"

LOL!

>
> Joe

Matt


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to