• 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

Still need "glue" to connect JSF and Entities ?

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear all Java EE users,
in the last few years I have been using JBoss Seam to avoid writing boilerplate code, for example if I need to save some form data I'd prefer
referencing directly the Entity objects, instead of writing Managed Beans, just to transport the form data.

I'd like to know if it's possible with Java EE 6 to perform the same thing, and thus use a portable approach.

Thanks a lot
Paul
 
Saloon Keeper
Posts: 27763
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Paul!

I never have gotten as deeply into Seam as I should, but the main reason why you shouldn't bind Domain Model objects directly as JSF backing beans is that it's too inflexible. If you're only going to use the entity as a single, immutable reference, it works, but when you start talking updating - or worse yet, switching the backing bean to a different instance of the same entity - things start going downhill in a hurry.

J2EE is not really designed for cheap monolithic development. That's what ASP and PHP are for. J2EE works better when you have a large, complex design and you want to implement it in small, easily manageable pieces. Lots and lots of pieces, sometimes, but the important part is that they're all relatively simple, so when you dump them on the next trainee, he/she won't have to spend a week figuring out what all the ramifications are.
 
reply
    Bookmark Topic Watch Topic
  • New Topic