On 4/18/06, Ted Husted <[EMAIL PROTECTED]> wrote: > I would tend to disagree. I feel that the separate of concerns between > XWork and a web application front end are important. I don't believe > it would be helpful to start lumping things back together again.
Providing Struts users with a complete, cohesive API doesn't preclude this separation. > I do think one problem is that our approach to referring to XWork in > the WW book and documentation is inconsistent. There is a tendency to > refer to everything as WebWork when it is not. Moving forward, I think > we simply need to be more carefult to say XWork when we mean XWork and > SAF when we mean SAF, and perhaps just refer to "the framework" when > we do not care to make the distinction. This is exactly what I'm talking about. 99.9% of users (100% of Struts users) don't care about this separation, and they have trouble with it. Even the authors have trouble keeping it straight. > No, Struts Action 2.0 will *not* require Java 1.5. I'm sure some > future release will increment the platform, but right now, most > everyone I know is using Java 1.4 in production. Action 2.0 is meant > to be something that we can all start using in production now. Without saying whether we should support 1.4 or not, realistically we're talking about Struts 2.0.0 in production some time after August depending how long it takes users to port their applications, not right now, at this moment, right? JDK 1.6 comes out in the fall at which point 1.4 will be two major releases behind. We must embrace 1.5. We should keep in mind that: - 1.4 support will add complexity and require more development time - 1.4 will become less relevant pretty quickly - 1.4 users have two other options: Struts 1.2 and WebWork 2.2 Bob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
