>I hope I've been able to present my concerns and arguments in
>at least a partially understandable way. I am open to discussion
>on this, but unfortunately, I feel at this time that the end result
>should be that struts not impose the ONE controller solution on us.
Let me rephrase what I understood of ypur concerns to see wether I
got your focal point:
Your main issue is that you want to be able to build large modular
webapps with each sub-webapp being separately maintain-/develop-/deployable
rather than providing one large monolithic webapp.
Assuming my above rephrasing does correctly capture your concerns here
are my comments on it:
I agree with that requirement.
I also believe it should be possibly to achieve that using the current
design without too much additional hazzle.
How about the following quick and dirty idea:
Make all your separate sub-webapps independend webapps. Each of these
does need some "gate" to be entered from one of the other apps. Also
add "transition points" into your sub-webapps to act as stepping stones.
AFAICT you'll need such "gates" anyway since you have to define
interfaces between your sub-webapps even when allowing for different
controllers, set of action-mappings etc.
You may have to add a custom taglib like the 'app' taglib from the
example application to handle the transition but I believe it could
be done.
At a later point in time this may be further supported by struts
by allowing dynamically reloading the action-mapping of a webapp.
By means of this we could modularize action-mappings which might
help to achieve the above design goal.
Of course this is just a quick shot and very likely needs further
refinement. However it should help as a general idea.
>Although others may disagree, I cannot say that struts 1.0 is
>ready for final release until the single-controller limitation is
>removed. Removing the limitation *may* require some changes that
>are not backward compatible and therefore should be made sooner
>rather than later.
I do disagree.
I do this mostly on the basis that I don't value the restrictions
you point out as being that important. After all your requirements
seem to be rather complex and way beyond what most current webapps
need (don't get me wrong - that doesn't make these requirements
invalid).
Second I'm not yet convinced your requirements can't be satiesfied
(to an acceptable degree) by the design as it is just now.
Third I do believe it just is about time to release a (basic)
framework that does solve most users needs to have a solid platform
to continue further development (i.e. toward 1.1, 1.2, ...2.0)
My thoughts, best,
Michael
--
Vote against SPAM - see http://www.politik-digital.de/spam/
Michael Gerdau email: [EMAIL PROTECTED]
Just say NO! to Microsoft Windows.
PGP-keys available on request or at public keyserver
