At 11:59 AM -0500 3/14/04, Ted Husted wrote:
On Fri, 12 Mar 2004 15:07:18 -0600, Joe Germuska wrote:
....

 Is now a good time to coin a "StrutsContext" class that
 encapsulates the various arguments to "execute"?  I've always kind
 of wanted this for Action too.  I've frequently thought it would be
 a nice thing. This seems to get a little blurry when looking
 forward to a more chain-oriented Struts, where there's already a
 Context object floating through, but it seems worth discussing if
 we're making a new interface.

I'd say that this is a good time to introduce a StrutsContext -AND- make Struts Chain the default request processor.

No one is more gung-ho about Struts Chain than I am, but people should be aware that we're still just into beta with functionality. Using it on my latest project, I've definitely found a few pieces that hadn't yet been implemented. I've put in what I found missing -- tiles and file upload -- but there are probably some other less mainstream pieces that will turn out to be buggy or not even implemented. We would probably want to make a branching CVS tag for this if we do it. I don't have a lot of experience working on branched codebases with a distributed team, so it should be an interesting ride, but I think Struts Chain is far enough from ready that we don't have a choice.


Plus, we need to push commons-chain to a full release. And what about commons-resources? That sounded like it was pretty close. Looking at http://jakarta.apache.org/struts/status.html , I think that roadmap may be still be a good strategy -- get the resources transition done for 1.3, then the new request processor for 1.4. Can anyone summarize what's standing between here and moving to commons-resources?

In general, I'm satisfied with targeting the "page prep" as a chain-dependent feature. If we introduce a StrutsContext as the chain implementation of o.a.c.chain.Context then we'll have to come up with a Context factory process so that the ComposableRequestProcessor can be given a Context instead of instantiating one itself. My first hunch is that it should be an early chain command which creates a sub-context of a specific type and uses it to do most of the chain processing.

Joe

--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin


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



Reply via email to