• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Paul Clapham
  • Devaka Cooray
  • Bear Bibeault
Sheriffs:
  • Junilu Lacar
  • Knute Snortum
  • Liutauras Vilda
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Piet Souris
Bartenders:
  • salvin francis
  • Carey Brown
  • Frits Walraven

Spring in Action: 3rd edition - Questions on Spring

 
Ranch Hand
Posts: 300
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Craig,
I read the last edition of Spring In Action and was greatly impressed with it.
I don't work directly with Spring and my interest is to compare it to alternatives from an architectural perspective?

I have a few questions:
1.
Say you have the classic requirement to change the look the feel for different users in a CMS.
You have a choice Spring themes of JSF / Facelets. In a JSF / Facelets architecture you could just store references to CSS files as variables that were in backing beans and then resolve this as a dynamic property in a JSF page. Seems very simple. If I use themes I need to know about a lot of specific configuration and it just seems a more clunky wa of doing it. What's your preference for dynamic look and feel and why?

2.
JSF is now pushing facelets and not JSPs as a view technology. Spring is still pusing JSP as the default technology. Why is this? JSPs are a bit clunky and not good for promoting a true view layer (with no controller logic sneaking in).

3.
Spring originally started out as an alternative to EJB because the earlier EJB specs were way too clunky and nearly everyone went for Servlet centric architectures.
Now, EJB has got much simplier (especially with the advent of CDi) and Spring in an effort to p[rovide more and more features looks to be getting clunkier and clunkier. To even do a simple Hello World requires Apache jars not contained in Spring. Do you think there's a danger that Spring could be forgetting about it's original intent to simplify rather than to complicate things?

4.
The JSF model is much component based; whereas Spring MVC is much more request based. Which do you think is a better model and why?

5.
If you were asked for the number one killer feature from spring what would it be?

Reason I ask this is because a lot of what Spring does: Aspects, JMX seem like they can be achieved without it.

Cheers.

 
I found a beautiful pie. And a tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
    Bookmark Topic Watch Topic
  • New Topic