Mastering in ejb pdf

All rights reserved. Published simultaneously in Canada. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections or of the United States Copy- right Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Rosewood Drive, Danvers, MA , , fax This publication is designed to provide accurate and authoritative information in regard to the subject matter covered.

It is sold with the understanding that the publisher is not engaged in professional services. If professional advice or other expert assistance is required, the services of a competent professional person should be sought. Many have commented that the first edition was one of the best technical books they ever read. We took a big risk in developing the second edition of this book and decided to build the book on the Web.

We received feedback from around the world when writing this book, and thus we have an evolving list of contributors and reviewers.

The list is too large to mention here but is available at www. The ServerSide. I remember sitting in my cubicle at Trilogy Software, an e-commerce company in Austin, Texas, lost in deep middleware thoughts. My challenge was to devise an interesting load-bal- ancing strategy for our in-house application server, which we called the back- bone. The backbone was a superb software system.

It was cleanly written, easy to use, and boasted some very high-end features — features such as distributed object support, object-relational mapping, and extensible domain object mod- eling. It had almost anything you needed for Internet development. It was a worthy investment for Trilogy. I was part of a task force to add enterprise features to this backbone, such as transaction control, security, and load-balancing.

Our goal was to improve the backbone into a product worthy of large-scale deployment. So that day, after hours of racking my brain, I finally finished crafting what I believed to be a highly creative and optimal load-balancing strategy.

Court is one of those developers who can really pick apart almost any design and expose its flaws — a unique quality that only a few developers I know have. We turned the design inside and out, mark- ing up my freshly printed hard copy with scribbles and other unintelligible comments that only we could understand.

Finally, satisfied that we had reached a conclusion, I thanked Court and walked toward the door, prepared to implement the changes we had agreed upon. Court said something to me that would change my way of thinking.

His comment baffled and confused me at first, but would eventually result in a complete paradigm shift and career move for me. What did Court say? Enterprise JavaBeans? Something like regular JavaBeans? Eventually, Court managed to explain to me what EJB was. And once he explained it, I knew that Trilogy had to do a degree turn or lose its competitive advantage. You see, EJB is a specification for a server-side component marketplace.

EJB enables you to purchase off-the-shelf components from one vendor, combine them with components from another vendor, and run those components in an application server written by yet a third vendor. This means companies can collaborate on the server side. EJB enables you to buy, rather than build, ele- ments of server-side applications. The EJB value proposition had strong ramifications for Trilogy. EJB repre- sented a way for Trilogy to get out of the middleware business and concentrate on its e-commerce strategic efforts.

This proposition would eventually lead to Trilogy forming an entirely new business unit. I decided to start researching EJB and pushing for Trilogy to adopt it. Back then, the specification was about a third of the size it is today. Understanding the specification turned out to be much more challenging than downloading it.

The specification was written for system-level vendors and was not meant to be a tutorial for end developers. The section on entity beans, for example, took me a good two months to really grasp, as the notion of per- sistent components was new to me.

This arduous struggle with understanding the EJB specification is what even- tually led me to write this book for you.

You'll learn the concepts and techniques for authoring distributed, enterprise components in Java from the ground up. Covering basic through advanced subjects, Mastering Enterprise JavaBeans 3. Four new chapters and one new appendix cover the latest features of this new release, and in-depth coverage of the Java Persistence API and the entities defined therein is provided.

The authors' main goal is to get you programming with EJB immediately. Wiley Technology Publishing Timely. Visit the companion Web site at www. Get BOOK.