On Wed, 29 Dec 2004 10:21:24 -0500, Ted Husted <[EMAIL PROTECTED]> wrote:
> On Wed, 22 Dec 2004 17:21:46 -0600, Joe Germuska wrote:
> > I haven't felt like there's a clear consensus on how to move such a
> > thing forward, and I guess I'm still in "ask permission" mode
> > instead of "ask forgiveness" mode.   I'm not really even sure how
> > to move it forward in small measured steps to get people looking at
> > something concrete for reactions.
> 
> On the Milestones page [http://struts.apache.org/milestones.html], there are 
> actually two "API Beans". Once for the server-side and one for the view-side:
> 
> * ActionContext - A Commons Chain Context that implements the Action class 
> logical API (same signatures).
> 
> * ViewContext - A Commons Chain Context that implements the combined 
> VelocityStruts logical API (same signatures).
> 
> Perhaps it would help if we could come to a consensus on the Roadmap, or used 
> the Roadmap to forge a consensus. (I have no illusions about getting this 
> page right the first time.)
> 
> Does anyone disagree with the Roadmap [http://struts.apache.org/roadmap.html] 
> or Milestones [http://struts.apache.org/milestones.html] ?
> 

In general, I'm OK with what's listed there. I would point out,
though, that we seem to be discussing "Consider a 'smart' action
type", listed under 1.5, at the moment, potentially as part of 1.3.
(I'm not suggesting that we necessarily defer it, just pointing out
the discrepancy.)

There are a few points that I don't necessarily agree with, but
they're all phrased as "Consider X". I can't argue with considering
them, although I might argue against actually doing them. ;-)

One particular area on which I am not in sync with some others is the
whole JSF thing. I have no problem with Struts providing support for
JSF, but I am not in favour of "adopt[ing] JSF strongly", as Craig put
it. Craig and I see the future differently. He, I believe, sees JSF as
the future (which is not entirely surprising ;), whereas I see JSF and
other page oriented technologies as the past. The future, as I see it,
is in highly dynamic apps.

So what I'd like to see in a Struts 2.0 is strong support for highly
dynamic apps.This might include handling requests submitted as XML,
support for "serialising" to JavaScript or XML, etc.

--
Martin Cooper


> Is there anything someone would like put differently?
> 
> -Ted.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

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

Reply via email to