[ann] WebWork 1.0 released
Short version: WebWork 1.0 has been released. If you're into building web apps in Java you need to check it out. End of story. Go here and download ASAP: http://sourceforge.net/projects/webwork Slighly longer version: I'm proud to announce the release of WebWork 1.0! WebWork is a HMVC web application framework in Java, developed as Open Source (BSD license) and designed to help create dynamic websites using minimal effort and maximum flexibility. It's architecture is easy to learn and understand, yet has features that allow for complex applications to be built. One of the main features is it's total separation between the controller and view aspects of an application, thus allowing for a multitude of view technologies to be utilized. Out of the box WebWork has support for JSP (and comes with an extensive tag library that covers most needs), XSLT, and the template engine Velocity. Adding support for more such tools is very easy (the Velocity integration was done in hours), allowing you to have maximum flexibility with regard to how you structure your application. You also get to choose whether you want to use a Model-1 or Model-2 approach to building applications, although we'd recommend using both as is described in our comprehensive documentation that includes reference sheets (for the tag library and expression language) and many useful tipstricks sections. WebWork comes with a comprehensive set of examples that are both used to test the functionality of the framework, as well as showcase how it can be used. Many examples are conversions from other frameworks (such as Struts) so that you can see firsthand how WebWork differs from the rest of the crowd. One of the most important tasks when working with frameworks like this is the configuration step, which is where Java classes are mapped to logical names (used for invocation) and where the connection between controller and view (such as a JSP or Velocity template) is made. This configuration can be done manually, but to ease this process there is an XDoclet extension available (through the XDoclet project, see http://xdoclet.sourceforge.net) that will allow you to specify all such configuration directly in your Java code using custom WebWork-specific JavaDoc tags. XDoclet is also used to generate HTML documentation of your application, which helps to serve as a communication channel between the Java developer and web designer (if those roles are separated into several team members). There are a multitude of other unique and interesting features that we are very excited about, but we'd encourage you to download and find out about those yourself. So get it now from: http://sourceforge.net/project/showfiles.php?group_id=14797 Documentation can be found in the download, or online at: http://213.203.18.31/ We encourage you to try WebWork together with the wonderful SiteMesh (http://www.opensymphony.com) and XDoclet tools, a combination which can give you an amazing productivity and clean application architeture. This is an OpenSource project, developed using an open development process, and is hosted by SourceForge. If you have any questions we recommend the user mailing list, and if you have suggestions for improvements we're all ears on the development mailing list, both of which can be found on the project homepage at: http://sourceforge.net/projects/webwork If you are attending JavaOne this year, then you might want to stop by our WebWork developer meeting on Wednesday March 27, 6.30pm at Fourth street Bar Deli (across from the Metreon). See ya there :-) /Rickard Öberg, WebWork project manager -- Rickard Öberg Author of Mastering RMI Chief Architect, TheServerSide.com The Middleware Company - We Build Experts! === To unsubscribe: mailto [EMAIL PROTECTED] with body: signoff JSP-INTEREST. For digest: mailto [EMAIL PROTECTED] with body: set JSP-INTEREST DIGEST. Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
Re: [ann] WebWork 1.0 released
On Fri, 22 Mar 2002 09:26:40 -0500, M. Simms [EMAIL PROTECTED] wrote: Why would this be better than STRUTS which has taken about 10 man years of effort and the expertise of many heavyweights to build and debug ? Somehow the above argument is not quite logical. The amount of man years or expertise of heavyweights means nothing if the basic foundation is bad. But sure, if you want to play that game WW has approximately 10 man years of effort put into it as well (10 registered developers, plus patch submissions from about 10 more, 1 year of development), and being a lead developer on both JBoss and XDoclet I wouldn't consider myself lightweight exactly. But this is a nonsensical argument. I would encourage you download it and take a look at the examples and documentation before passing any swift judgments. You might actually like it ;-) /Rickard === To unsubscribe: mailto [EMAIL PROTECTED] with body: signoff JSP-INTEREST. For digest: mailto [EMAIL PROTECTED] with body: set JSP-INTEREST DIGEST. Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
Re: [ann] WebWork 1.0 released
On Fri, 22 Mar 2002 10:09:14 -0600, Haseltine, Celeste I have not seen WebWork, but to answer your question, Struts is a very heavy framework in that the Jakarta tag libraries are very tightly integrated into the MVC architecture portion of Struts. For those of us who use JSP tag libraries that either come with our Servlet containers, or choose to use other tag libraries than those bundled with Struts, then Struts is not a good option. Since I prefer to use the tag libraries that come bundled with my JSP/Servlet container, I need a stand alone MVC architecture, that I can integrate my servlet containers tag libraries into. If WebWork is such a stand alone MVC architecture, then it is one I would consider using over Struts. I certainly think you'd be able to use MVC given the above. The main point of integration between the WebWork servlet dispatcher (if you choose the Model-2 mode that is) is the value stack that holds the objects that can be rendered in the view (e.g. JSP). You can access this stack from the request object directly, or bind the action that was executed to a request attribute by wrapping your code with the following: webwork:property value=. id=action .. your JSP code goes here. The attribute action holds the action object: %=((MyAction)request.getAttribute(action)).getFoo()% /webwork:property Is that good enough? We certainly do recommend that you use the provided tag library to access the data, but if you want to use your own tags there's a multitude of ways to accomplish that, depending on your particular scenario. /Rickard === To unsubscribe: mailto [EMAIL PROTECTED] with body: signoff JSP-INTEREST. For digest: mailto [EMAIL PROTECTED] with body: set JSP-INTEREST DIGEST. Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
Re: [ann] WebWork 1.0 released
On Fri, 22 Mar 2002 17:32:47 -0500, M. Simms [EMAIL PROTECTED] wrote: I certainly will ! I was just testing to see how passionate you guys were about this effort and you passed the test. I was not going to waste my time if there was little or no response. LOL, good one ;-) Well, I most certainly wouldn't want you to waste time, and it is my firm belief that this isn't once of those. A lightweight STRUTs is certainly an excellent idea...and whose time has come. Amen to that! (Why didn't Sun think of that ?) Because lightweight sun is an oxymoron? ;-) /Rickard === To unsubscribe: mailto [EMAIL PROTECTED] with body: signoff JSP-INTEREST. For digest: mailto [EMAIL PROTECTED] with body: set JSP-INTEREST DIGEST. Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
JSP as a resource
I have a servlet that wants to output the result of a JSP page, but the JSP is not available as a regular page but as a resource in the JAR of the servlet (which resides in /WEB-INF/lib). Is it possible for the servlet to retrieve the contents of the packaged JSP page, and somehow send it to JSP for compilation and output the result. Or do I have to unpackage the page so that it is available the usual way? /Rickard -- Rickard Öberg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com === To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
jsp:include and path info
Hi! I am fiddling with a Model-2 framework (yeah, yet another one). It is going well except for one thing. I have decided to give the action name as extra path info to the servlet, like this (where "action" has been mapped to my dispatcher servlet): /servlet/action/DoStuff?foo=bar i.e. invoke DoStuff action with foo parameter set to bar. So far so good. However, in the JSP that is delegated to after DoStuff execution I have a jsp:include that can either point to another action or to another plain jsp, like this: jsp:include page="/servlet/action/OtherStuff" flush="true"/ or simply: jsp:include page="somepage.jsp" flush="true"/ However, it seems like this is invoked with the servlet set to "/servlet/action" and the path info to "DoStuff", i.e. the original info. So, is it possible to call subpages like this? How do I do to get the right path info propagated? Or, do I have to change to a parameter based scheme: /servlet/action?action=DoStuff This works, but is uglier... Any ideas? regards, Rickard === To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
