| |
Struts and Sparx both create industrial-strength applications
Struts is a great Framework. Just like Sparx, Struts was designed to support complex industrial-strength web applications. However, Struts simply requires too many JSP and HTML pages and too many lines of Java code just to perform simple data entry and navigation tasks. Many programmers integrate other templating systems like Tiles to help simplify Struts development but end up struggling with multiple open source code packages that still require too much HTML and Java to do anything useful.
What does Sparx do that Struts doesn't?
Because Struts is designed only for the navigation, controller, and dispatcher portions of your applications, it has the following shortcomings:
- Struts doesn't help you with your user interface's design (navigation styles, links, look and feel, etc.). You'll need a good HTML designer or be content with UI's that will not impress your users.
- Struts doesn't support built-in login, multiple attempts lockout, logout, and timeout. You'll have to write authentication code yourself.
- Struts doesn't support automated sitemap generation.
- Struts doesn't support complex server-side field and form validations without extra Java code or additional libraries.
- Struts doesn't support sophisticated client-side validation, conditionals, keypress filters, and data formatting. You'll have to write your own JavaScript.
- Struts doesn't support any database operations. You'll need to find and integrate a persistence framework.
- Struts doesn't support role-based personalized applications (security) without writing your own authorization code.
- Struts has relatively new and limited support for subsites and sub-applications.
- Struts doesn't support creating libraries of inheritable and reusable pages, forms, fields, validations, business rules/values, and commands. You have limited reuse options.
- Sparx eliminates up to 90% of HTML, Java, and JavaScript code required by Struts.
|
