[ANN] AppFuse 1.8.1 Released
This release is mostly a bug fix release with no new features. It also includes many upgrades to the core libraries (Hibernate, Spring, iBATIS, MyFaces). Thanks to all the sponsors who have contributed products and free hosting to the AppFuse project. You guys rock!
To see how AppFuse works, please see the following demos:
- Demo of Features in Flash
- Struts + Spring + Hibernate
- Spring + iBATIS
- WebWork + Spring + Hibernate
- JSF + Spring + Hibernate
- Tapestry + Spring + Hibernate
Comments and issues can be sent to the mailing list or posted to the AppFuse Issue Tracker.
Posted by Anatol Pomozov on June 16, 2005 at 02:07 AM MDT #
Posted by 126.96.36.199 on June 16, 2005 at 07:37 AM MDT #
If the Wicket team can make those results competitive with the rest of the frameworks, I'll consider it.
Posted by Matt Raible on June 16, 2005 at 10:35 AM MDT #
-- begin rant --
I can't conclude from that article that folks don't want another framework. Some of them don't. Others do.
I can tell you why I wanted another framework (and ended up being active for one). model 2 web frameworks suck!. I am saying this as an architect, who sees developers struggle with 'model 2' frameworks every day. They do not encourage good coding, no matter how well you try to manage that (and unfortunately, JSF is not going to help here either). They do not help with reusability, giving us problems with projects that have slightly different versions. Code duplication all over. And I could go on like this for ages. When I joined Wicket (as a user), I wasn't looking for fun, fame, or whatever. I was looking for a solution to the many problems we encounter on a daily basis when working with Java to build web applications.
The last three projects that were started at the shop where I work were .NET projects. And they are doing good. Sure the devs complain that they like Eclipse better etc, but the end of the day, they deliver faster and more focussed on customer needs. Now, the shop that I work for still believes Java is superiour for most of our projects, but we need to get better development performance and maintainability etc when building java webapps.
Your idea of enterprise ready sure is not mine. You base it on the idea that something has to be popular to be good, and that companies will only use technology that they have heard of. In many cases they don't care. And they shouldn't, as long as the job gets done properly. And as for the developers... when we hire people (and we do that on a regular basis), we are solely interested in whether they are smart, fit the team, and for experienced people, whether they can handle OO right. As for the frameworks... we just expect a developer to learn one within a couple of days or maybe a week or two. Period.
-- end rant --
I regret that I didn't give Tapestry a chance a couple of years ago. The learning curve is high (the major reason for the existence of Wicket), but if we were a Tapestry oriented instead of a Struts/Webwork/Maverick oriented shop now, we wouldn't have had a lot of the problems we experience today.
Now that I've said this all, I don't think you should put Wicket in AppFuse. If you would, you should also put in Echo for sure. What I do think you should do, is to protect the world and throw out the model 2 frameworks :) Just have Tapestry and JSF, and add Wicket and Echo when they are popular enough.
Posted by Eelco on June 16, 2005 at 12:31 PM MDT #
Posted by Lars Fischer on June 16, 2005 at 04:14 PM MDT #
Posted by Eelco on June 16, 2005 at 05:24 PM MDT #
Posted by Mark Johnson on June 24, 2005 at 02:30 PM MDT #
Acegi does a lot to simplify deployment of AppFuse - in any app server. You shouldn't need to configure any authentication settings anymore - just the JNDI DataSource. If you do want to customize the login query or something similar, you can modify web/WEB-INF/applicationContext-security.xml.
Posted by Matt Raible on June 26, 2005 at 10:25 PM MDT #