Spring mvc against seam

Spring mvc is the foundation that has been there for a long time; it's a well-documented and proven technology. Many websites use spring.

Seam is a framework based on jsf-rich faces implementation. It has many ajax based components. He uses some heavy things like EJB, JPA. All this is error prone, and this structure is so slow (it is almost impossible to develop something on my computer because it is very slow, especially redistributing to jboss) But this is very good for back office applications.

Does anyone have professional experience in these two frameworks? Can you recommend the best option? Why?

Hi

+5
source share
5

: Spring -MVC (2.5) Seam

Seam Java Server Faces ( ), , . ( JSF - , ). :

-

view >> controller >> service >> domain

Seam

view >> service >> domain

( , Seam Framework)

No controller, No service

view >> domain 

,

  • JSF 2 JSR 303 - Bean
  • Wicket JSF,
  • -.
  • Spring DI,

Spring -MVC

-

  • ( , )
  • ( , )
  • Spring 3.0 (JSR 303 - Bean Validation, )

Spring 3.0,

  • ( ) MultiActionController, - xml, ( MultiActionController @Component)
  • SimpleFormController , Spring 3.0

...

, , .

+7

Seam, . . POJOs EJBs, , EJBs . Tomcat JBoss. Tomcat . Spring MVC .

+1

Seam POJOS - Hibernate, Tomcat. , "" . , , . iframe - , . , . Tomcat struts 1.2 spring mvc. 50 .

+1

Seam 3 Spring 3. Seam 3 , , . Spring .

0

All Articles