Comments on: WebWork 2: The sleeping giant http://almaer.com/blog/webwork-2-the-sleeping-giant blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Glen Stampoultzis http://almaer.com/blog/webwork-2-the-sleeping-giant/comment-page-1#comment-26100 Glen Stampoultzis Thu, 25 Aug 2005 05:32:58 +0000 http://almaer.com/blog2/webwork-2-the-sleeping-giant#comment-26100 Not to take away from WW but people might also be interested to know Tapestry 4 also supports Portlets. I haven't tried it myself but the implementation looks pretty easy to use. Not to take away from WW but people might also be interested to know Tapestry 4 also supports Portlets. I haven’t tried it myself but the implementation looks pretty easy to use.

]]> By: Matt Dowell http://almaer.com/blog/webwork-2-the-sleeping-giant/comment-page-1#comment-26099 Matt Dowell Wed, 24 Aug 2005 22:40:27 +0000 http://almaer.com/blog2/webwork-2-the-sleeping-giant#comment-26099 Matt: I agree completely. It's so frustrating that the project has a very vibrant user community but the lead developer dissapears for months at a time. I am a big proponent of someone just forking the thing and taking it over. It's so frustrating that I have started looking at www.extremecomponents.org. Matt: I agree completely. It’s so frustrating that the project has a very vibrant user community but the lead developer dissapears for months at a time. I am a big proponent of someone just forking the thing and taking it over.

It’s so frustrating that I have started looking at http://www.extremecomponents.org.

]]> By: Matt Raible http://almaer.com/blog/webwork-2-the-sleeping-giant/comment-page-1#comment-26098 Matt Raible Wed, 24 Aug 2005 21:34:47 +0000 http://almaer.com/blog2/webwork-2-the-sleeping-giant#comment-26098 The problem with Display Tag is that Fabrizio Giustina re-wrote the whole thing and is the primary developer on the project. However, he doesn't seem to want to do any support on the mailing lists or forums. I try to help out on the mailing lists when I can, but it seems like I'm one of the few. If I knew the code better (i.e. I wrote it), I might be inclined to help out more. Another example of a open source project that's not very developer-friendly. User friendly, yes, b/c it works - but it seems like it's hard to contribute. At least to me. The problem with Display Tag is that Fabrizio Giustina re-wrote the whole thing and is the primary developer on the project. However, he doesn’t seem to want to do any support on the mailing lists or forums. I try to help out on the mailing lists when I can, but it seems like I’m one of the few. If I knew the code better (i.e. I wrote it), I might be inclined to help out more. Another example of a open source project that’s not very developer-friendly. User friendly, yes, b/c it works – but it seems like it’s hard to contribute. At least to me.

]]> By: Matt Dowell http://almaer.com/blog/webwork-2-the-sleeping-giant/comment-page-1#comment-26097 Matt Dowell Wed, 24 Aug 2005 21:11:02 +0000 http://almaer.com/blog2/webwork-2-the-sleeping-giant#comment-26097 The AJAX taglibs in WW2.2 looks great. I am currently in the process of converting from 2.0. They have also made the syntax for referencing objects within JSP even simpler. The next thing I would love to see from WW2 is a fork of the Displaytag library integrated into thier taglibs. There is no one at the rudder for Displaytag. The AJAX taglibs in WW2.2 looks great. I am currently in the process of converting from 2.0. They have also made the syntax for referencing objects within JSP even simpler.

The next thing I would love to see from WW2 is a fork of the Displaytag library integrated into thier taglibs. There is no one at the rudder for Displaytag.

]]> By: Don Brown http://almaer.com/blog/webwork-2-the-sleeping-giant/comment-page-1#comment-26096 Don Brown Wed, 24 Aug 2005 20:22:32 +0000 http://almaer.com/blog2/webwork-2-the-sleeping-giant#comment-26096 Agreed, and this is why Struts Ti, a proposal for the successor to Struts classic currently in the Struts sandbox, is building directly on top of WebWork 2. We are hoping to combine WebWork with RoR ideas, Spring IoC, Beehive's Page Flow, and some rapid development ideas from Cocoon to lower the learning curve for web development. Furthermore, there is no intrinsic reason JSF or a another component-based view technology is incompatible with WebWork2. JSF is weak already on the controller layer as it was designed to focus on the view, so I think there is still a need for a robust controller technology, be it Shale, Webwork2 or hopefully Struts Ti for JSF applications. Agreed, and this is why Struts Ti, a proposal for the successor to Struts classic currently in the Struts sandbox, is building directly on top of WebWork 2. We are hoping to combine WebWork with RoR ideas, Spring IoC, Beehive’s Page Flow, and some rapid development ideas from Cocoon to lower the learning curve for web development.

Furthermore, there is no intrinsic reason JSF or a another component-based view technology is incompatible with WebWork2. JSF is weak already on the controller layer as it was designed to focus on the view, so I think there is still a need for a robust controller technology, be it Shale, Webwork2 or hopefully Struts Ti for JSF applications.

]]>