> -----Original Message----- > From: Hani Suleiman [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 9:29 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] XW/WW2 "press release" text for review > > > 1) I don't see the need to cuss webwork1.
I didn't see it that way. I remember several discussions back and forth about feature implementations and whether they should maintain the web-agnosticism or be specifically tailored to web applications, since that's what most people were doing. I think what I said was honest and not derogatory. > 2) The portlet sentence seems rather bizarre to me, a portal > dispatcher? JSR-168 says very little about portals, so a portal > dispatcher is certainly not self-explanatory, to me at any rate. It's what Rickard was talking about. It's basically a Portlet that acts as a dispatcher for Xwork to call Actions by translating the PortletRequest the same way the ServletDispatcher does. > 3) 'Two strategies for handling form submission' seems another odd > detail to choose to highlight. Smells too much of 'look at > how clever > we are for coming up with this trick!' rather than 'this is why the > average person should use webwork2'. Point taken, I'll tone that down. > 4) 'JPublish is replacing their...'...JPublish isn't a bunch > of guys, > it's a product. > 5) I assume the sig is not part of the press release > > On Monday, August 18, 2003, at 09:15 PM, Jason Carreira wrote: > > > I've written up a short "press release" to go as an announcement to > > TSS and JavaLobby and on the OpenSymphony site. Take a look > at let me > > know what you think: > > > > The OpenSymphony team is proud to announce the first beta > releases of > > XWork 1.0 and WebWork 2.0. > > > > This is the first release of a complete rewrite of WebWork, a > > hierarchical pull-MVC framework. While WebWork 1 provided a good > > separation of the general command framework from the web specific > > code, there was always a tension between making the code > more specific for > > web > > applications and keeping the web-agnostic general command > > implementation. With XWork, the OpenSymphony team went back to the > > drawing board to create a powerful generic command pattern > > implementation. WebWork2 leverages the power of XWork at > its core and > > builds upon it with web application framework specific code. This > > separation allows for each project to specialize and do what it does > > best without the possibility of contaminating or limiting > either code > > base. > > > > XWork > > > > Xwork is a generic command pattern implementation with no > dependencies > > on web specific libraries. Xwork adds powerful features to command > > processing including interceptors, the OGNL (http://www.ognl.org) > > expression language, an IoC (Inversion of Control) > container, flexible > > type conversion, and a powerful validation framework. > > > > - Interceptors allow arbitrary code to be included in the call stack > > for > > your Action before and/or after processing of the Action, which can > > vastly simplify your code itself and provide excellent > opportunities > > for > > code reuse. Many of the features of XWork and WebWork 2 are > implemented > > as Interceptors and can be applied via external > configuration along > > with > > your own Interceptors in whatever order you specify for any set of > > Actions you define. > > > > - OGNL is used throughout XWork to allow dynamic object graph > > traversal and method execution where needed and can transparently > > access properties from multiple beans using our ValueStack. > > > > - XWork IoC allows for code dependencies to be made explicit and > > centrally managed while simplifying your Action code. Components > > required by your actions will be instantiated and maintained in a > > hierarchy of three scopes (application <- session <- > request) and will > > be provided to your actions automatically, removing the need for > > boilerplate code to lookup required services from a registry or > > hardwired dependencies on a service implementation class. > > > > - The XWork Validation Framework allows you to define your > validations > > for a class in external XML files and have them applied at runtime > > automatically (using an Interceptor). It is very flexible > framework, > > allowing for different validations for the same class in different > > contexts with defaults and inherited validations and passing the > > validation context on to your domain objects to allow them to be > > validated using their own validation definitions. It also > ties in with > > XWork's excellent i18n localization for multi-language messages. > > > > XWork is completely generic, and can be applied to any > > request/response paradigm. JPublish is currently replacing > their internal command > > pattern > > implementation with XWork, and possible future > implementations built on > > XWork include a Portal Dispatcher implemented as a JSR-168 > Portlet, a > > JMS dispatcher, and JSF integration. > > > > WebWork2 > > > > WebWork2 is built as a set of Interceptors, Results, and > Dispatchers > > on top of XWork. WebWork2's view technologies include JSP, > Velocity, > > and FreeMarker. For the final 2.0 release, JasperReports > and XSLT views > > will > > be implemented as well. WebWork2 comes with a small but > powerful set of > > JSP tags and Velocity macros which make use of OGNL's > expression parser > > and XWork's ValueStack to provide for easy and expressive web page > > development. WebWork2's JSP tags and Velocity macros are > built upon a > > flexible templating system, allowing you to customize the > output of the > > tags by providing your own set of templates. WebWork2 also > comes with > > powerful pre-built components to make web application development > > faster > > and easier such as two strategies for handling duplicate > form submits > > (one returns an error view for subsequent form submissions, > the other > > saves the result of the first form processing and displays > that result > > for all subsequent form submissions). WebWork2 also provides the > > standard web application framework features such as servlet > redirect > > and > > request dispatcher results and multipart file uploading support. > > > > -- > > Jason Carreira > > Technical Architect, Notiva Corp. > > phone: 585.240.2793 > > fax: 585.272.8118 > > email: [EMAIL PROTECTED] > > --- > > Notiva - optimizing trade relationships (tm) > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by: Free pre-built ASP.NET > sites including > > Data Reports, E-commerce, Portals, and Forums are available now. > > Download today and enter to win an XBOX or Visual Studio .NET. > > http://aspnet.click-url.com/go/psa00100003ave/ > > direct;at.aspnet_072303_01/01 > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites > including Data Reports, E-commerce, Portals, and Forums are > available now. Download today and enter to win an XBOX or > Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet _072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
