Why SlimWeb

  • The ultimate in flexibility -- no limits on what you can do and how you can do it. Use the plain old form submit/page reload model, or AJAX, or a mix of the two. Use any component or JavaScript framework on the Internet that you like. Mix and match paradigms, libraries and components as you see fit.
  • The ultimate in portability -- works with any Java web container (Tomcat, Jetty, etc), and of course on any J2EE-compliant application server. If you've ever tried moving a JSF application from GlassFish to Weblogic, you'll totally appreciate SlimWeb's simplified deployment.
  • Lean and Mean -- Small means easy to learn, and easy to use. A new developer can be productive with SlimWeb in a fraction of the time necessary to  link building learn JSF or Struts. The framework runtime consists of a single  lead generation 100K jar file.
  • Setting it up is trivial
  •  Convention over Configuration -- In most cases SlimWeb figures out all it needs to know by itself. No need for you to ever see a faces-config.xml or struts.xml configuration file again!
  • Cleaner Controller/Model? separation -- in JSF/Struts the controller (the backing bean/struts action respectively) also  best weight loss pills serves as a proxy between the  Fredericksburg DUI lawyer view and the model. Later, when you submit a form the user input is bound to controller properties again. No need for such hacks in SlimWeb, where those problems are solved in a simpler, cleaner and truly elegant way.
  • JSON friendly -- embed JSON data in rendered pages, or serve JSON right from your actions to support ordinary AJAX scenarios.
  • Alternative JVM Languages -- you're not limited to Java when developing your models/views/controllers. SlimWeb is fully compatible with  Groovy,  Scala and  Stal. Other JVM languages (Jython, Clojure, etc) can be used to some extent, but SlimWeb works best with languages that map their classes to Java classes, with full support for Java annotations. Groovy and Scala match these requirements.
  • EJB friendly -- access your legacy EJBs via dependency injection (in a future SlimWeb version...) just like you would in a JSF application, but remember: EJBs make no sense in new projects.
  • Eliminate the need for EJBs -- Get rid of your EJBs! Without sacrificing scalability, of course. Shorten your build cycles, simplify your deployment, but most importantly simplify your application by moving your business logic from Enterprise Java Beans to plain old Java. SlimWeb will help you with all your persistence needs, automatic transaction management is included by  Truck Accident Lawyer default, if you want it.

Developing a SlimWeb application feels more working with TurboGears or Ruby on Rails than developing a traditional J2EE solution. You can expect shallow learning curves and greatly improved productivity which are rarely seen in the Java universe.

When not to use SlimWeb

JSF claims that a Java programmer can develop a rich web application with little need for HTML, CSS or Javascript expertise. We, the SlimWeb team, consider this an oxymoron. You do need some command of HTML/CSS/Javascript to develop anything but the most straightforward of applications. It is way more important to be able to write your own HTML/CSS/JavaScript and/or easily reuse any third-party component or library - leverage the web to its full potential, rather than be able to drag and drop components visually. JSF with its prebuilt components does simplify some tasks for some  Truck Accident Lawyer developers. Dragging and dropping components via a visual designer is a nice marketing pitch. But the costs it forces you to pay in complexity, steep learning curves, and reduced flexibility (try customizing the behavior of a JSF component on the client side!) are just too great and outweigh the gains many times over.

Use JSF for your application if it's extremely well understood in advance. Set in stone, preferably. And if it's simple enough that the  Portable Stage provided JSF components will do the job. And hope you'll never need to do anything not foreseen by your component  iphone photography authors.

Use SlimWeb in all other  coach bags cases.