Spring MVC Web Framework versus Struts

Thanks :) ok I read the reference for Spring MVC.
So if I do not misunderstand the reference it means
that:

1. you can suit in some way the workflow of the DispatcherServlet
namely when declaring some special beans used by that dispatcher
(showed in table 13.1.)

2. that you can nearly extend and suit everything in Spring MVC
from high till low level parts of Spring MVC because it is based
on interfaces what is very flexible and you can change the standard
implementation by referencing to your own implementation of that
interfaces (in the WebApplicationContext and ApplicationContext
or the web.xml).

Is it correct?

Quote:

---

First of all, struts 2.x is a completely different animal than struts 1.x. Struts 2.x is based on Webwork 2.2.x

---

is this a suicide???, :rolleyes:
why change the sintaxis???
http://struts.apache.org/2.0.6/docs/home.html

read again tuttorials, maybe buy a book,
think this is waste of time, i cant see a good reason

Quote:

---

Expert Spring MVC and Web Flow

---

good book, i read all, but is out of date for SWF, but i can suggest: buy the book :)

spring mvc and SWF a powerful combination, make easier your life

a good question could be,
what thing you not like about springmvc/SWF ???

i am happy with both, but i dont like the pretty hell with integration springmvc and jasperreprots for example

regards and thanks for the developers for this beautiful product :D

nice job guys!!!

Quote:

---

Is it correct?

---

That's a pretty accurate summary.

Erwin

I prefer JSF than Struts (both 1.x and 2.x) and SpringMVC, especially when it is used with Facelets, Ajax4jsf, some third party JSF components (like RichFaces which is still lack of some common components such as calendar, file upload, ...) and Spring Web Flow (although I cannot find any document about using SWF 1.0.3 with Ajax4jsf. Hope things will be better with SWF 1.1).

As long as we have JSF, I think here should be an option for JBoss Seams.
Not that I like that IMHO 'marketacture' framework, but some folks do and it would be interesting to see some preliminary statistics.

Wow! Great. Thank you for some idea that you give about MVC. It's help me a lot.

Debug Enable in windows

rem # Sample JPDA settings for remote socket debugging
set "JAVA_OPTS=%JAVA_OPTS% -Xrunjdwp:transport=dt_socket,address=8787,server=y ,suspend=n"

Quote:

---

Originally Posted by Keith Donald

To second Rod here:

Spring Web Flow (SWF) is not built on top of Spring MVC: the two framework compliment each other in a loosely coupled manner. More specifically, Spring MVC can delegate to SWF for flow execution via a thin adaption layer, and that's how it's always been designed (and will stay that way).

SWF is a pure controller framework focused primarily on solving the problem of managing stateful web conversations (dialogs) in a elegant manner, providing a self-contained flow engine based on a finite-state machine.

Spring MVC is a request-driven MVC framework positioned very much as a Struts+1, with a more complete data binding facility and more extensibility points than what's offered by Struts.

SWF fills the "C" in the MVC -- SWF is not a replacement for Spring MVC, it's a "C" compliment.

Keith

---

Impossible to explain better, I totally agree.