> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Bob Lee > Sent: Tuesday, April 18, 2006 9:56 PM > To: Struts Developers List; [EMAIL PROTECTED] > Subject: Re: XWork and Struts Action 2.0 > > > 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. >
As a new user of WebWork 2.2 I dont see much of XWork except for the xwork.xml file. So I agree totally. This is not to say that as an advanced user, one day I might decide to exploit an XWork feature. > > 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: > Keep in mind the corporate business side of things. The Java EE 5.0 specification is still not released yet. > - 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 > Of course waiting for Java EE 5.0 and EJB 3.0 holds things up significantly if you are deploying to WebLogic Server 8.1 which is halfway to J2EE 1.4 in the first place. In other corporates cannot make the jump to Java 5 because they are waiting on Java EE 5.0 application server to be certified! Of course this may not apply to you if you are using JBoss and/or Tomcat! -- Peter Pilgrim :: J2EE Software Development & Architecture Operations/IT - Credit Suisse Group - "One Bank", Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom Tel: +44-(0)207-883-4497 ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ============================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
