RE: [OS-webwork] XW/WW2 "press release" text for review
Hello, Your "press release" gave a lot of good information on XWork and WW2 (well, at least for me the new user of WW1.3 anyways)... the highlighting of the separation is definitely a great finding for us. I found your writing informative and helpful, and the first paragraph below is great too! I think we'll make the switch in the near future... hopefully some good tutorials and good samples are already out (haven't looked just yet)! Cheers, James -Original Message- From: Jason Carreira [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2003 10:52 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] XW/WW2 "press release" text for review Ok, gotcha. Try this for the first paragraph: This is the first release of a complete rewrite of WebWork, a hierarchical pull-MVC framework. Many web frameworks suffer from being tightly coupled to the Servlet spec when it is not necessary, especially Struts. This makes both unit testing your command components (Actions in Xwork / WebWork) and reusing them outside a web application very difficult or impossible. With XWork, the OpenSymphony team went back to the drawing board to create a powerful generic command pattern implementation which makes unit testing and code reuse much simpler. 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. > -Original Message- > From: Hani Suleiman [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 10:16 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] XW/WW2 "press release" text for review > > > > On Monday, August 18, 2003, at 09:56 PM, Jason Carreira wrote: > > > > > > >> -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. > > > Well, if you want to highlight how it beats existing > solutions/architectures, then pick on Struts. Picking on webwork1 as > the 'problem' solution seems silly. Attack the competition, not your > own products. What you said IS honest, I'm not saying you're being > dishonest, just that from a marketing perspective, I don't > think it's a > smart move. When BEA releases a new version, they don't say 'well > version 7 sucked, so we came up with version 8', they say > 'oracle/websphere suck, and the cool things we added to version 8 fix > all THEIR problems' > > > > --- > 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/psa0013ave/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/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code4 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] XW/WW2 "press release" text for review
Sounds like a great idea. Joe Ottinger monitors this list, and he's the J2EE editor for JDJ, so he's the man to talk to :-) > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 19, 2003 9:39 AM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] XW/WW2 "press release" text for review > > > Having just started working with WW2/XW, and liking it very > much, an associate and I were thinking of putting together > something also. Perhaps rather than a pure web-based > tutorial (like Tracy is doing), we can present it in the form > of an article / series of articles in order to reach an > audience that has not yet found out about WebWork - > explaining the features as well as a "how-to". I think this > would be very complimentary to the upcoming book and > web-based tutorial. > > /Ian > > -- > From Down & Around, Inc. > Innovative IT solutions > Software Architecture * Design * Development > ~~ > web:www.fdar.com > email: [EMAIL PROTECTED] > phone: 617.821.5430 ~~ > > > > > > > -Original Message- > > > From: Rickard Öberg [mailto:[EMAIL PROTECTED] > > > > > > I thought the writing was pretty good. I on the other hand > > > question the > > > need for boasting about a beta. It'd be weird to do a press > > > release now, > > > and then a similar one in a week or two when the final > release is out. > > > > > > /Rickard > > > > > > Well, I don't see the problem with promoting WW2 at beta > and release. > > My > > question, and the reason I'm hesitant now to send this out, > is the introductory > > tutorial. I think we need this for new users coming in to > get up to speed > > quickly. > > > > > > Tracy, if you have something in some pre-release form, go ahead and > > put it up on > > the Wiki, and lets have everyone take a look and work on it > together. If we > > could get this finished up in the next couple of days, we > could send out the > > press release and get some people looking at WW2. > > > > Jason > > > > > > --- > > 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/psa0013ave/direct;at.aspnet_072303_ > > 01/01 > > ___ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > --- > This SF.net email is sponsored by Dice.com. > Did you know that Dice has over 25,000 tech jobs available > today? From careers in IT to Engineering to Tech Sales, Dice > has tech jobs from the best hiring companies. > http://www.dice.com/index.epl?rel_code=104 > > ___ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > --- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code4 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] XW/WW2 "press release" text for review
I've updated the text to reflect that you are just adding support for Xwork actions to Jpublish. > -Original Message- > From: Anthony Eden [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 19, 2003 11:29 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] XW/WW2 "press release" text for review > > > I am not replacing the command framework in JPublish with > XWork. I was > considering it at one point but have decided not to make that change. > > Sincerely, > Anthony Eden --- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code4 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] XW/WW2 "press release" text for review
Cameron, JPublish users requested that the current JPublish Action API be kept while still allowing for XWork to be used from within JPublish. That is the current design and that is how it will stay for JPublish 3.x. Sincerely, Anthony Eden Cameron Braid wrote: Since you want us to know this, can you please indicate why you have made this decision ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Eden Sent: Wednesday, 20 August 2003 1:29 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] XW/WW2 "press release" text for review I am not replacing the command framework in JPublish with XWork. I was considering it at one point but have decided not to make that change. Sincerely, Anthony Eden 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 strateg
RE: [OS-webwork] XW/WW2 "press release" text for review
Having just started working with WW2/XW, and liking it very much, an associate and I were thinking of putting together something also. Perhaps rather than a pure web-based tutorial (like Tracy is doing), we can present it in the form of an article / series of articles in order to reach an audience that has not yet found out about WebWork - explaining the features as well as a "how-to". I think this would be very complimentary to the upcoming book and web-based tutorial. /Ian -- >From Down & Around, Inc. Innovative IT solutions Software Architecture * Design * Development ~~ web:www.fdar.com email: [EMAIL PROTECTED] phone: 617.821.5430 ~~ > > > > -Original Message- > > From: Rickard Öberg [mailto:[EMAIL PROTECTED] > > > > I thought the writing was pretty good. I on the other hand > > question the > > need for boasting about a beta. It'd be weird to do a press > > release now, > > and then a similar one in a week or two when the final release is out. > > > > /Rickard > > > Well, I don't see the problem with promoting WW2 at beta and release. My > question, and the reason I'm hesitant now to send this out, is the introductory > tutorial. I think we need this for new users coming in to get up to speed > quickly. > > > Tracy, if you have something in some pre-release form, go ahead and put it up on > the Wiki, and lets have everyone take a look and work on it together. If we > could get this finished up in the next couple of days, we could send out the > press release and get some people looking at WW2. > > Jason > > > --- > 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/psa0013ave/direct;at.aspnet_072303_01/01 > ___ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] XW/WW2 "press release" text for review
Ok, ok... We'll save it for the final release. > -Original Message- > From: Pat Lightbody [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 19, 2003 10:34 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] XW/WW2 "press release" text for review > > > > I thought the writing was pretty good. I on the other hand question > > the > > need for boasting about a beta. It'd be weird to do a press > release now, > > and then a similar one in a week or two when the final > release is out. > > +1 on that :) > > > --- > This SF.net email is sponsored by Dice.com. > Did you know that Dice has over 25,000 tech jobs available > today? From careers in IT to Engineering to Tech Sales, Dice > has tech jobs from the best hiring companies. > http://www.dice.com/index.epl?rel_code=104 > > ___ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > --- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code4 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] XW/WW2 "press release" text for review
> I thought the writing was pretty good. I on the other hand question the > need for boasting about a beta. It'd be weird to do a press release now, > and then a similar one in a week or two when the final release is out. +1 on that :) --- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] XW/WW2 "press release" text for review
Since you want us to know this, can you please indicate why you have made this decision ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Eden Sent: Wednesday, 20 August 2003 1:29 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] XW/WW2 "press release" text for review I am not replacing the command framework in JPublish with XWork. I was considering it at one point but have decided not to make that change. Sincerely, Anthony Eden 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 fo
Re: [OS-webwork] XW/WW2 "press release" text for review
I am not replacing the command framework in JPublish with XWork. I was considering it at one point but have decided not to make that change. Sincerely, Anthony Eden 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
RE: [OS-webwork] XW/WW2 "press release" text for review
> -Original Message- > From: Rickard Öberg [mailto:[EMAIL PROTECTED] > > I thought the writing was pretty good. I on the other hand > question the > need for boasting about a beta. It'd be weird to do a press > release now, > and then a similar one in a week or two when the final release is out. > > /Rickard Well, I don't see the problem with promoting WW2 at beta and release. My question, and the reason I'm hesitant now to send this out, is the introductory tutorial. I think we need this for new users coming in to get up to speed quickly. Tracy, if you have something in some pre-release form, go ahead and put it up on the Wiki, and lets have everyone take a look and work on it together. If we could get this finished up in the next couple of days, we could send out the press release and get some people looking at WW2. Jason --- 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] XW/WW2 "press release" text for review
Hani Suleiman wrote: 1) I don't see the need to cuss webwork1. He's not cussing WebWork. He's explaining what is and why it is. 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'd be the equivalent of a servlet dispatcher but adapted to the portlet API. For example, it'd have to deal with separated action/rendering phases, which WW2 is perfectly adapted for right now (IMO). 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'. I didn't see it that way. 4) 'JPublish is replacing their...'...JPublish isn't a bunch of guys, it's a product. True. Replace "their" with "its". I thought the writing was pretty good. I on the other hand question the need for boasting about a beta. It'd be weird to do a press release now, and then a similar one in a week or two when the final release is out. /Rickard --- 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] XW/WW2 "press release" text for review
After it's done, I'll put it in JDJ :) On Tue, 19 Aug 2003, Mike Cannon-Brookes wrote: > I agree with Hani's points - but must add that on the whole this is awesome! > Very solid, lots of text, good points made throughout. > > I know Hani meant to commend you on the overall quality, but forgot (or he > hadn't taken his bile hat off ;)). > > M > > On 19/8/03 11:29 AM, "Hani Suleiman" ([EMAIL PROTECTED]) penned the words: > > > 1) I don't see the need to cuss webwork1. > > 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. > > 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'. > > 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, Jasp
RE: [OS-webwork] XW/WW2 "press release" text for review
Ok, gotcha. Try this for the first paragraph: This is the first release of a complete rewrite of WebWork, a hierarchical pull-MVC framework. Many web frameworks suffer from being tightly coupled to the Servlet spec when it is not necessary, especially Struts. This makes both unit testing your command components (Actions in Xwork / WebWork) and reusing them outside a web application very difficult or impossible. With XWork, the OpenSymphony team went back to the drawing board to create a powerful generic command pattern implementation which makes unit testing and code reuse much simpler. 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. > -Original Message- > From: Hani Suleiman [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 10:16 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] XW/WW2 "press release" text for review > > > > On Monday, August 18, 2003, at 09:56 PM, Jason Carreira wrote: > > > > > > >> -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. > > > Well, if you want to highlight how it beats existing > solutions/architectures, then pick on Struts. Picking on webwork1 as > the 'problem' solution seems silly. Attack the competition, not your > own products. What you said IS honest, I'm not saying you're being > dishonest, just that from a marketing perspective, I don't > think it's a > smart move. When BEA releases a new version, they don't say 'well > version 7 sucked, so we came up with version 8', they say > 'oracle/websphere suck, and the cool things we added to version 8 fix > all THEIR problems' > > > > --- > 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/psa0013ave/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/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] XW/WW2 "press release" text for review
On Monday, August 18, 2003, at 09:56 PM, Jason Carreira wrote: -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. Well, if you want to highlight how it beats existing solutions/architectures, then pick on Struts. Picking on webwork1 as the 'problem' solution seems silly. Attack the competition, not your own products. What you said IS honest, I'm not saying you're being dishonest, just that from a marketing perspective, I don't think it's a smart move. When BEA releases a new version, they don't say 'well version 7 sucked, so we came up with version 8', they say 'oracle/websphere suck, and the cool things we added to version 8 fix all THEIR problems' --- 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/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
RE: [OS-webwork] XW/WW2 "press release" text for review
Here's some updated text: 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. The JPublish project is currently replacing its internal command pattern implementation with XWork, and possible future implementations built on XWork include a JSR-168 Portlet implementation as a Dispatcher for XWork, 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 a combination of a token JSP tag / macro and an Interceptor which prevent duplicate form submissions. WebWork2 also provides the standard web application framework features such as servlet redirect and request dispatcher results and multipart file uploading support. For release downloads, see the java.net project sites: http://xwork.dev.java.net http://webwork.dev.java.net Check out the project documentation on the OpenSymphony wiki: http://wiki.opensymphony.com/space/XWork http://wiki.opensymphony.com/space/WebWork2 For project issue tracking, see: http://jira.opensymphony.com/secure/Dashboard.jspa The project mailing list is available at [EMAIL PROTECTED] > -Original Message- > From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 9:59 PM > To: [EMAIL PROTECTED]; Hani > Suleiman; [EMAIL PROTECTED] > Subject: Re: [OS-webwork] XW/WW2 "press release" text for review > > > I agree with Hani's points - but must add that on th
RE: [OS-webwork] XW/WW2 "press release" text for review
> -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 differe
Re: [OS-webwork] XW/WW2 "press release" text for review
I agree with Hani's points - but must add that on the whole this is awesome! Very solid, lots of text, good points made throughout. I know Hani meant to commend you on the overall quality, but forgot (or he hadn't taken his bile hat off ;)). M On 19/8/03 11:29 AM, "Hani Suleiman" ([EMAIL PROTECTED]) penned the words: > 1) I don't see the need to cuss webwork1. > 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. > 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'. > 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 >> developmen
Re: [OS-webwork] XW/WW2 "press release" text for review
1) I don't see the need to cuss webwork1. 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. 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'. 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 a
[OS-webwork] XW/WW2 "press release" text for review
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/psa0013ave/direct;at.aspnet_072303_01/01 ___ Opensymphony-w
