This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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.
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’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com