MySpace


Sharanam Shah

Sharanam Shah


Last Updated: 6/3/2009

Send Message
Instant Message
Email to a Friend
Subscribe

Gender: Male
Status: Married
Age: 28
Sign: Capricorn

City: Mumbai
State: Maharashtra
Country: IN
Signup Date: 2/18/2006

Blog Archive
[Older      Newer]
 /  / 
Wednesday, June 03, 2009 

Category: Writing and Poetry


 
Designed for beginners and intermediate developers, this book teaches JPA from the ground up with an aim to get the reader up to speed with JPA as quickly as possible. It delves deeply into the core of the JPA, providing a sound understanding of the components that make up the framework and the way they interact with each other.

This book uses the learning by doing pattern with a lot of ready-to-use examples. This pattern has proven to be the best approach for learning a new technology. Most [if not all] of the concepts that you will find in this book are demonstrated using well described and easy to understand examples, yet sophisticated enough to demonstrate JPA in a real-world context.

This book demonstrates a step-by-step guide to developing Web as well as Enterprise applications [using EJB 3 ] which re-enforces all the learning that takes place throughout the book. It also teaches how to integrate an enterprise application with Struts2. Not only this, the book also introduces EJB 3.1 [a part of Java EE 6] and demonstrates developing a IPA based EIB 3.1 application with the help of Glassfish v3 Prelude.
 
What You'll Learn?
 
Building Web Applications
Using JSP/Servlets, DAO, JPA using Hibernate 3, Ajax, Glassfish v2
Using JSP, JPA using TopLink, Glassfish v2
Building Enterprise Applications
Using JSP/Servlets, EJB 3 - Session Beans, JPA using TopLink, Glassfish v2
Integrating an enterprise application with Struts2 [An extensible framework for creating enterprise-ready Java Web applications]
Building Enterprise Applications Using EJB 3.1
Using JSP/Servlets, EJB 3.1 - Session Beans, JPA using EclipseLink, Glassfish v3 Prelude
Using the NetBeans IDE to develop JPA based applications
Reverse Engineering POJOs and Mapping Documents from Database tables
Pagination using JPA

To ensure that the focus remains on understanding the technology, we have adopted the simplest and most customary domain models such as Customer, Authors, ContactDetails, Books, Subscribers and Guestbook.
 
Buy this item
 
ISBN 10: 81-8404-709-7
ISBN 13: 978-81-8404-709-7

Edition: First

Downloads
Sample Chapter                                                      TOC


THE TOPICS COVERED IN THE BOOK

Introduction
Persistence, Object/Relational Mapping And JPA, Introduction To Java Persistence API, Writing The First Application

Core Components Of JPA
Entity, Entity Manager And Its Factory, Transactions, Persistence Unit

Metadata
Getting Started With Metadata, Database Identity, Associations, Collections, Inheritance, Defining Metadata Using XML

The JPA Query Language
The Basics Of Java Persistence Query Language, Joins, Query Interface, Pagination, Named Queries, Native SQL Queries

Web Application Development
Customer Database Web Application, Subscriber Management Web Application
 
Enterprise Application Development
Introduction To EJB 3.0, Customer Database Enterprise Application, Integrating Customer Database Enterprise Application With Struts2

Enterprise Application Development Using EJB 3.1
Introduction To EJB 3.1, Customer Database Enterprise Application

Appendix
Installing The NetBeans IDE, Customer Database Application Using Different ORMs

CONTENTS OF THE CD-ROM
Setup files for JDK 6
NetBeans IDE 6.5
Hibernate Core 3.x
Hibernate Annotations 3.x
Hibernate EntityManager 3.x
Struts 2.x
MySQL Community Server 6.x
JDBC Drivers
Library files for:
Display Tags
EclipseLink
TopLink
OpenJPA
Source code for the examples covered in this book
Saturday, February 18, 2006 

Category: Web, HTML, Tech
An intranet is basically a private web based network. It uses all of the technology of the internet but is safe and protected behind a firewall that keeps unauthorized personnel out. Companies have been using them for years as a method of streamlining their internal communications.

Because a web browser can run on any type of computer, the need to maintain multiple paper copies of documents that are constantly changing can be eliminated. Documents like training manuals, internal phone books, procedure manuals, benefits information, employee handbooks, requisition forms, etc. can be maintained as electronic documents and updated at almost no cost. The savings in paper and other material costs can be significant

But the most powerful aspect of an intranet is its ability to display information in the same format to every computer being used. That allows all of the different software and databases a company uses to be available to all employees without any special equipment or software being installed on their systems.

This universal availability of information is sparking an era of collaboration unlike anything ever seen before. The departmental barriers that exist in many companies are slowing breaking down because now colleagues can share information readily using the company intranet.

Options for implementing an intranet

There are a variety of options for setting up an intranet. They include building your own intranet technology, purchasing and installing third-party software, or purchasing access through an extranet ASP. Here is a quick summary of the advantages and disadvantages of each approach:

1. Building it yourself
Advantages: Complete control of user interface design; ability to customize level of functionality; integration into internal systems, and direct access to user activity.

Disadvantages: High up-front development cost; requires staff expertise in the development of extranets, commitment of internal staff for 6 months to a year for planning, execution, review and implementation; and an ongoing commitment of internal staff for internal and client support, hosting, maintenance and upgrades.

2. Purchasing/installing third-party software
Advantages: Proven track-record of packaged solution; ability to choose functions and to
customize user interface, more rapid implementation compared to building it yourself.

Disadvantages: High up-front purchase cost; commitment of internal staff for customization and implementation; on-going commitment of internal staff for internal and client support, hosting, maintenance and upgrades; and extensive internal and client training

3. Using a Service Provider (ASP)
Advantages: Proven track-record of the application; low cost of entry and predictable cost over time; virtually immediate implementation; no commitment of internal staff for internal support, hosting, or maintenance; and upgrades at no cost by extranet experts, and savings on internal server use.

Disadvantages: Less freedom in user interface design, and fixed functionality.

In the final analysis?
The approach you choose depends on how you work, the technical and financial resources at your disposal, and how rapidly you need to move forward.

Sharanam Shah (DOT) COM