Yep, that's a lot of what I had in mind. But I had been thinking that there was call for some more functionality in the controller layers as well as in the view. The interface is read-only, which is right for a view, but maybe incomplete in other layers.

But I'm ready for bed now, so I will have to sleep on it before I could say just what "write" type methods I think there would need to be.

Joe


At 11:16 PM -0500 11/30/04, Ted Husted wrote:
On Tue, 30 Nov 2004 17:15:51 -0600, Joe Germuska wrote:
�I've been thinking for a while that we should stop storing so many
�things directly in the ServletContext and instead, define a
�"Struts" object which would hold these things. �I've mentioned this
�obliquely a few times and not gotten much response, so maybe no one
�else likes the idea. �Or maybe it's been too oblique. �Benefits of
�something like this would be reducing dependencies on the Servlet
�API and providing a better environment for testing.

Like it? I implemented it two years nine months ago :)

* http://svn.apache.org/viewcvs.cgi/struts/trunk/src/share/org/apache/struts/config/ConfigHelperInterface.java?rev=48889&view=markup

It's also mentioned on the proposed updates to the Roadmap.

* http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=29427

under the moniker "ViewContext".

I was going to try and work on updating the website tonight, but my flight was delayed, and I might not get to it.

I do think we should be passing a Struts API bean out to the view, which could also include a context for arbitrary properties.

-Ted.



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


--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction"  -The Ex

Reply via email to