Domain: mc4j.org
Stories and comments across the archive that link to mc4j.org.
Comments · 7
-
My next framework is Stripes
It's like Webwork/Struts 2, but without configuration files.
http://mc4j.org/confluence/display/stripes/Home -
Re:Ever used Eclipse?
While you're checking out Java on the server make sure to take a look at Stripes. It is a great web framework that makes life soooo much easier.
-
Re:In Ur Face, Novell
I haven't tried JSF, but I'm the sole maintainer of a Struts application. It works reliably, but changes are a pain in the behind.
I have zero experience with the Stripes web framework, but this comparison between Stripes and Struts has an excellent illustration of the klunkiness of Struts: http://stripes.mc4j.org/confluence/display/stripes /Stripes+vs.+Struts
"One of my prime frustrations with Struts is the fact that just to implement a single page/form, I have to write or edit so many files. And I have to keep them in sync, or else things start going horribly wrong. With Struts I have to write my JSP, my Action, my Form, a form-bean stanza in the struts-config.xml, an action stanza in the struts-config.xml, and if I'm going to do it the Struts way, a bunch of forward stanzas. And let's not go into the fact that since this is all stored in one xml file I'm continually facing merge conflicts with my team mates. Yes, there are annotations for Struts, but they are just literal translations of what's in the XML file, and they don't feel natural to me."
You may with to learn Struts anyway, because it's so common. But if you're builing a new Java web app from scratch and no one on your team is used to Struts, I'd investigate alternatives. The Struts project page even lists a few under the 'Similar Projects' heading. Now, extensibility, stability, and other buzzwords matter just as much as ease of initial configuration. So don't use speed of initial development as your sole criteria. -
Stripes: Good web framework for teaching
You might like to consider Stripes as the web framework for the course. One individual recently switched to using it to teach a masters level course in Java web development (at a university in Nice, France).
On the plus side it:
- Has comprehensive and easy to follow documentation
- Is much simpler to grasp for new developers than Struts, JSF etc.
- Is more OO than most MVC web frameworks, without forcing a component model on you
- Doesn't require gobs of XML (or other) configuration -
Re:Struts - A Possible Cure-all?
If you like Struts you should check out Stripes. It performs a similar function but it is much easier to configure and maintain.
-
Try it, you'll like it!Life is SOOOO much easier when you separate your program logic from the view. For a long time I resisted thinking there wasn't much point. Now I use JSP for presentation only. All logic goes into Java objects that JSP can pull data from but I avoid doing any data writes from JSP. With the model and view separated I can easily change what gets displayed on a web page without worrying about breaking the program logic. As long as I don't remove access to any data that gets displayed I can update program logic without messing up the pages. It's much easier to read both. The JSP pages are mostly just HTML with some JSP tags in them. The Java code doesn't have any HTML in it at all.
BTW, if you're looking for a nice framework for Java web development I highly recommend Stripes. I stumbled across it last year and it is much nicer to use than Struts!
-
Re:When?
If you have to use Java, a copy-cat framework for Java is Trails. The linked articles make it look pretty impressive.
Another relatively unknown java framework I've flirted with very recently is Stripes. It's claim to fame is that its configuration is annotation based. Dev consists of the view and action, no worrying about an xml file to sync between the two.