Autres vendeurs sur Amazon
+ EUR 0,01 (livraison)
Expert One–on–One J2EE Development without EJB (Anglais) Broché – 18 juin 2004
|Neuf à partir de||Occasion à partir de|
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Les clients ayant acheté cet article ont également acheté
Description du produit
Revue de presse
a valuable learning experience all round (Application Development Advisor, 1st September, 2004)
Présentation de l'éditeur
Expert One–on–One J2EE Development without EJB shows Java developers and architects how to build robust J2EE applications without having to use Enterprise JavaBeans (EJB). This practical, code–intensive guide provides best practices for using simpler and more effective methods and tools, including JavaServer pages, servlets, and lightweight frameworks.
What does this book cover?
The book begins by examining the limits of EJB technology what it does well and not so well. Then the authors guide you through alternatives to EJB that you can use to create higher quality applications faster and at lower cost both agile methods as well as new classes of tools that have evolved over the past few years.
They then dive into the details, showing solutions based on the lightweight framework they pioneered on SourceForge one of the most innovative open source communities. They demonstrate how to leverage practical techniques and tools, including the popular open source Spring Framework and Hibernate. This book also guides you through productive solutions to core problems, such as transaction management, persistence, remoting, and Web tier design. You will examine how these alternatives affect testing, performance, and scalability, and discover how lightweight architectures can slash time and effort on many projects.
What will you learn from this book?
Here are some details on what you′ll find in this book:
- How to find the simplest and most maintainable architecture for your application
- Effective transaction management without EJB
- How to solve common problems in enterprise software development using AOP and Inversion of Control
- Web tier design and the place of the Web tier in a well–designed J2EE application
- Effective data access techniques for J2EE applications with JDBC, Hibernate, and JDO
- How to leverage open source products to improve productivity and reduce custom coding
- How to design for optimal performance and scalability
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
Il n'y a pour l'instant aucun commentaire client
|5 étoiles (0%)|
|4 étoiles (0%)|
|3 étoiles (0%)|
|2 étoiles (0%)|
|1 étoile (0%)|
Évaluer ce produit
Commentaires client les plus utiles sur Amazon.com
I will tell you right away that this is not an anti-EJB book
that tries to prove you a case against EJBs. This is not a
cheap "Spring" framework promotion book either. This is a very mature expert one-on-one advice that is well worth getting.
Rod gives you a nicely rounded manual how to architect solid J2EE application using the latest and greatest practical solutions available both through the open source and JSR community. He propagates two extremly important ideas:
Lightweight containers and (simplified) Aspect Oriented Programming. Moreover, ha makes a very strong case for the application of Inversion of Control principle (IoC) in your applications. If you are not familiar with IoC: I see it pretty much as a savior to a J2EE technology. J2EE grew incredibly big, complex and fluffy in the recent years, and is at risk of being outflanked by more simplistic .NET solutions.
IoC offers "back to basics" approach where you as a good OO architect focus on the solid business domain model without poluting it with the infrastructure code. Through IoC supporting methods (such as Aspects) you then externalize the infrastructural pieces (transactions, pooling, persitence, logging, auditing,...) that make you apps run in the enterprise environement.
Rod's book gave me a very good basis for the creation of my own state-of-the-art J2EE solution and I am grateful for it. It is the best thirty-some dollars that I spent in the long time.
One more thing, this book in NOT a re-write of his previos book "J2EE Design and Development". I have both and they are not the same. I think you have to have both on your bookshelf in order to get the full treatment.
This is the second book in a series of 3, the first being Expert One-on-One J2EE Design and Development (Programmer to Programmer) and the final being Professional Java Development with the Spring Framework.
While the promises of J2EE have been busted long ago, this book clearly articulates why and better still, suggests reasonable and sound alternatives.
I find it repetitive in most areas; some people may feel repetition drives home the message, but it just gets tedious for me.
And although the bookcover promises to be more code intensive, I find it not to be. But then again, this is a book about architectural decisions and solutions for J2EE; and not about how to program.
This book (and the Spring framework) are the light at the end of the tunnel. The concepts are grounded in commonly accepted best practices for application development, the arguments for the implementations chosen are sound, and the implementations themselves are simple and fast. Not to mention, the entire framework has been designed so that you can drop it at any moment and move on to the next big thing when it arrives. Try getting that out of an EJB implementation.
Spring has given me hope for enterprise Java development. If you are at all interested in simplifying your life as a Java developer and have become disillusioned or disappointed with EJB, then this book is a must have.
The author is clear, logical, seems to have an all-encompassing knowledge
of J2EE technologies (so he's not just spouting propaganda for one
product) and his advice is grounded in the real world.