Amritendu De

author
+ Follow
since Feb 21, 2009
Amritendu likes ...
Oracle Java
Merit badge: grant badges
Biography
After completing his computer science engineering degree, Amritendu De spent a decade working in IT industry. He has worked for organizations like HP, IBM and Oracle in different capacities and currently working with a leading multinational as a Software Architect. He has worked extensively on Java and related technologies in his career. He was part of end-to-end product development for CRM, Utilities and Data Center Infrastructure Management business domains. He holds Sun Certified Enterprise Architect (SCEA) certification. In free time, he likes to watch movies and read detective stories.
For More
Nashville, TN
Cows and Likes
Cows
Total received
11
In last 30 days
0
Total given
0
Likes
Total received
10
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Amritendu De

There is no one size fits all solution. My book is on OCMJEA 5 but the assignment remains same. I would suggest you go through the problem more than once. Understanding the problem is the key. Search old posts on your assignment and see how people in this forum have approached the problem. It will help you get some idea how to proceed. In my book there are suggestions on how to approach the problem and pick up technology choices for example I would suggest stick to Oracle products for the solution. Lastly be simple in your approach and document all your assumptions. Lot of people have passed the certification and there's no reason why you will not. Best of luck!!
This can be achieved with orphanRemoval=true. You can see detailed code given in my book.
Spring 4 and Hibernate 4.

Instructions on code download given in the book.
9 years ago
I agree with Dave. You can have Single table inheritance with 2 classes. Junior and Senior could be the discriminator.
If you choose to make it unidirectional, you just need the @OneToMany and the @JoinColumn annotations. If you make it bidirectional, you also need the @ManyToOne annotation. This is given very clearly in my recent book.
Look at the book description on Amazon page. It is very detailed.
I selected Maven because of its popularity and most developers would find it useful. It is not that difficult using Eclipse Maven plugin.

However you can migrate the code to Gradle. There is no Java and JavaScript code dependency with Maven. Its just the structure and the dependencies.
When I say basics I mean you have experience in building web applications and if you are given a responsibility to build an app on your own you should be comfortable doing that.
It depends. I have seen lot of projects where unit testing is completely skipped because of budget. But it is highly recommended for high quality and regression.
The book only talks about building with Maven. It does not talk about Jenkins at all. Only the development part is covered and as a developer how you can deploy to Tomcat and test the application.
I have heard about this concept but did not have a chance to work on it or read the book. But yes the book is about building a service oriented REST API kind of design. The usefulness of this book comes when you come up with a domain model while solving a story in agile development and have to build on top of that domain model. All the variations of the domain model and its possibilities are described in minute detail. This is something the other books do not cover.
Actually it depends on the reader. I have chosen an architecture which is widely used nowadays and shown you the design areas you need go through when developing a relational database web application. The entire code is given as a download. So you can keep reading one chapter and browse the whole code for that chapter till you get every bit of it. I think that's the way the reader would be able to appreciate the design concepts and apply the same when designing or developing the applications in a similar architecture or a different architecture. You will find lot of articles on the net covering entity design or a full stack CRUD design. In this book I have covered all the relationships and shown you how to design the entity, business service, data access and presentation tiers. Also the user interface using JSP and JQuery/Ajax/JSON. Once you get the entire concept in this book, you can apply the same in a different technology of your choice. In conventional bottom up design model, we come up with the domain model first and then we develop on top of it using domain driven design.
The buzzword is SMAC - Social, Mobile, Analytics, Cloud. You need to direct your career in these technologies but first you need to get your basics right.