|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
| |||||||||||||||
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über den Autor
› Besuchen Sie die Seite von Floyd Marinescu auf Amazon
Produktbeschreibungen
Pressestimmen
Kurzbeschreibung
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
When first designing Enterprise JavaBean (EJB) systems, choosing a correct architecture, or partitioning of logic, that satisfies project concerns, such as performance, maintainability, and portability, is one of most difficult tasks faced by developers. Lesen Sie die erste Seite
Wortanzeiger
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Kundenrezensionen
Yes: 1. This one supports the EJB2.0 specification - whereas most of the others describe EJB1.1-patterns. A couple of them are invalid with the newer specification.
2. There are new patterns like transaction patterns and primary key generation strategies which are worth reading.
But: It is redundant in the description of well-known patterns like SessionFacade, DataTransferObject/Factory, EJBHomeFactory and BusinessDelegate - it doesn't add too much new insight, here. And it isn't easy to find these insights - Marinescu just cites the other patterns but doesn't describe the differences.
Pattern description fill about half of the book. The other half talks more on processes (how you get to an EJB design), best practices (using Ant and JUnit in the context of EJBs) and discussing replacements for EntityBeans (like JDO).
This is the weak part of the book. It should go more into details where it stays on the surface: The design process for the sample application is described too briefly and too weak to transfer it to my own application.
On the other hand, it goes too much into details where it could refer to an appendix: Is this an Ant-book, or what? 10 pages of Ant-scripts inlined but only 30 pages of EJB-code in a book about EJB-patterns???
Of course, this book will be a standard reference being cited everywhere. But it has a bible's drawbacks: Written not too clipped and precise, being very prose.
J2EE and EJB development. In my opinion EJB Design Patterns from
Floyd Marinescu is one of the best references for EJB Design Patterns
which covers all important topics about Pattern-Driven EJB development.
Floyd is Principal at "The MIDDLEWARE company" and one of the founders
of TheServerSide, the reference Portal for the J2EE community.
The book involves standard patterns like the Session Facade and
DTO (Data Transfer Objects) as well as extensions like a pattern
for asynchronous communication (Message Facade) between a client
application and the service layer in the middle tier.
The layered EJB architecture which includes the application, service,
domain, and persistence layer are discussed in detail. Useful hints
for the EJB development process and system design complete the book.
The book is a good choice for EJB developers and enterprise
architects.
One of the big advantages of the book are the chapters "From
requirements to Pattern-Driven Design" and "EJB development with
Jakarta Ant and unit testing with JUnit" which are dealing with
the solution of real world problems.
The chapter about Entity Beans vs. Java Data Objects (JDO) is a
must for every domain developer.
Floyd's book is well written and easy to understand for experienced
developers and architects. The Java source code examples of the book
are well documented and useful, if one desires a comlete impression
of EJB development.
To be honest, the book is one of the favourites in my bookshelf and
I consult it whenever possible to learn more about that important
technology.
The book also includes a nice poster that shows the EJB Design
Patterns and an additional text to avoid pit falls. It's nice to
stand in front of this poster and think about that great server
side Java technology.
Nachdem das Projekt nun erfolgreich beendet ist, habe ich mir dieses Buch gekauft und fast alle erfolgreichen Pattern unseres Projektes wiedergefunden. Hätte ich es doch gleich am Anfang gehabt.
Das Buch ist schnörkellos geschrieben und praxisnah, man erkennt sofort den Sinn des gerade erläuterten Patterns. Gut gefallen hat mir auch die Aufteilung und das Kapitel mit Code Snippets die eigentlich keine eigenständigen Pattern sind.
Das Buch ist auch ausgezeichnet als Nachschlagewerk geeignet. Ich würde das Buch jedem professionellen J2EE Entwickler empfehlen.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
|
