wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes Application Design Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Application Design" Watch "Application Design" New topic
Author

Application Design

Syed Saifuddin
Ranch Hand

Joined: Sep 01, 2003
Posts: 130
Dear All

I want to develop an application using JPA as ORM, Session Been as Business Layer and JSF as front end.
I started by DB design and generate JPA-Entity using my IDE. Now the second level is Session Bean.

My Question is about best practices. Either I have to put Entity-Manager in ORM Layer or to put it in Session Bean.

I am doing an enterprise Java EE6 application after a long time so if someone can reply in detail about standard and best practices, it will be more helpful.

Thank You & Best Regards,

Syed Saifuddin,
Senior Software Engineer

SAP Oracle AIX & Java Training
http://www.socialinet.com
Tim Cooke
Bartender

Joined: Mar 28, 2008
Posts: 858
    
  42

You're going against the most fundamental of "best practices" by deciding on your technology stack up front with no consideration about the business function of your application.

What I mean by this is how do you know if you need any of that stuff at all? JPA, Session Beans, JSF? What business or technical requirement is driving your decision to use these?

I recommend for starters that you StopCoding (<-- click). Get yourself a paper pad and a pencil and figure out what your application is supposed to do, and how you might go about doing it without writing a line of code. Only once you've done this do you understand the problem well enough to start coding.

Your solution should be the simplest thing that works. Don't reach for the tech tool big guns unless they solve a specific problem or make a difficult task easier. Often you just end up introducing enormous complexity to you application for no benefit at all.


Tim Driven Development
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Application Design
 
Similar Threads
opinion: Data Transfer Objects: pattern or anti-pattern (EJB3)
New to JSF : Interaction between JSF and EJB's
JSF EJB3 JPA , what are the design patterns. Most of design patterns of J2EE doesnt make sense..
modeling JSF managed beans on component diagram
What are the best web server for learning?