• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JBoss Seam

 
Ranch Hand
Posts: 425
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Folks,

I have just started looking at jboss seam to understand what benifits does it provide to the web application, which can be developed with Spring, JPA and jsf.
I did say Spring instead of Session beans because i am big fan of Spring.

My First observation was doesn't it make things more complicated by putting session beans and JSF action beans in one class. Also don't we loose the decoupling concept we learned in our basics.

I understand that i makes like simpler and there is less code to maintain now but i see a tradeoff which might or might not be worth the effort.

Any Comments on this ?

Thanks,
Rahul
 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Also don't we loose the decoupling concept we learned in our basics.



When you use seam, seam is the component which decouples your view from the model. All communication between your view and model goes through seam and hence it is quite easy to replace either of them with a different technology seamlessly
 
author
Posts: 1436
6
Python TypeScript Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In theory, you can "de-couple" everything into infinite number of layers -- it just a matter of how much de-coupling you actually NEED. If you really need to de-couple the JSF actions from EJB services, you can easily do that with Seam: Just make a POJO component that acts as JSF event handlers and make it invoke other service objects in the backend.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi , I also have such feeling that it may make different layer more couple.
e.g. ejb3 entity bean can be directly accessed in jsf . is it a good practice?
i.e. if anything in DB change will lead to change in ejb3 entity and presentation layer as well.
any comment ?
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"w wswwe"

Please click the "My Private Messages" link (at the top of this page) for a message from JavaRanch.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic