|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Enterprise JavaBeans 3.1
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| |||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt Enterprise JavaBeans 3.1 gegen einen Amazon-Gutschein in Höhe von EUR 9,45 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
|
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Andrew Lee Rubinger auf Amazon
› Besuchen Sie die Seite von Andrew Lee Rubinger auf Amazon
Produktbeschreibungen
Pressestimmen
"Alles in allem bekommt man ein sehr gutes Bild von EJB 3.1 und deren Möglichkeiten. Dieses Buch hat das Prädikat "Standardwerk" verdient – eben eines der besten Bücher über das Thema Enterprise Java Beans!" - www.php-nuke.de, März 2011 Lesen Sie die ausführliche Rezension unter: http://www.php-nuke.de/index.php?option=com_content&view=article&id=16&Itemid=9
Kurzbeschreibung
Learn how to code, package, deploy, and test functional Enterprise JavaBeans with the latest edition of this bestselling guide. Written by the developers of JBoss EJB 3.1, this book not only brings you up to speed on each component type and container service in this implementation, it also provides a workbook with several hands-on examples to help you gain immediate experience with these components. With version 3.1, EJB's server-side component model for building distributed business applications is simpler than ever. But it's still a complex technology that requires study and lots of practice to master. Enterprise JavaBeans 3.1 is the most complete reference on this specification. You'll find a straightforward, no-nonsense explanation of the underlying technology, including Java classes and interfaces, the component model, and the runtime behavior of EJB. * Develop your first EJBs with a hands-on walkthrough of EJB 3.1 concepts * Learn how to encapsulate business logic with Session Beans and Message-Driven Beans * Discover how to handle persistence through Entity Beans, the EntityManager, and the Java Persistence API * Understand EJB's container services such as dependency injection, concurrency, and interceptors * Integrate EJB with other technologies in the Java Enterprise Edition platform * Use examples with either the JBossAS, OpenEJB, or GlassFish v3 EJB Containers
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Tags, die Kunden mit diesem Produkt verbinden(Was ist das?)Klicken Sie zum Suchen verwandter Artikel, Diskussionen oder Personen auf ein Tag.
|
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
8 von 8 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
To buy an o'reilly book means that you want a good friend to help you on difficult terrain.
EJB is a complex field but this book is not the good friend you looked for, and this for two reasons:
1. It is not sufficiently proof read and contains a lot of errors in places where errors hurt much.
On p145 e.g. when you try to learn what exactly the merge of an entitymanager does, you find a code example that is heavily misleading in its last lines: 'dave.setname(...)' is NOT necessary. And that is crucial for understanding the concept. On p187 and on some other pages errors are just in the boldly typed parts. The 'references' are wrong although explicitly emphasized. If you try to learn something at such points in the book, prepare to be puzzled! And there are a lot of such points.
2. From p415 on there are only code examples (200 pages). This is not a problem per se as code can clear a lot of misunderstanding. But the code in this book is not well presented. It is VERY (!) blown up with low-quality doc-comments. On the other hand you get no explanatory text to tell you why things are made just so (remember: you are probably not yet an expert). You flip pages and pages in search for the flesh amongst the bones and you find neither flesh nor bones. The love and detail in the examples that I am used to from my other o'reilly books, is lacking here.
Attention: My comment aims for edition 3.1 of the book NOT for edition 3.0. The funny thing is that I chose to buy the book after having read some pages of edition 3.0 at 'google books' and 'paperc'. I liked version 3.0 and thought: why not just buy the newest edition? But somehow 3.1 is very different from 3.0, even part of the authors changed.
EJB is a complex field but this book is not the good friend you looked for, and this for two reasons:
1. It is not sufficiently proof read and contains a lot of errors in places where errors hurt much.
On p145 e.g. when you try to learn what exactly the merge of an entitymanager does, you find a code example that is heavily misleading in its last lines: 'dave.setname(...)' is NOT necessary. And that is crucial for understanding the concept. On p187 and on some other pages errors are just in the boldly typed parts. The 'references' are wrong although explicitly emphasized. If you try to learn something at such points in the book, prepare to be puzzled! And there are a lot of such points.
2. From p415 on there are only code examples (200 pages). This is not a problem per se as code can clear a lot of misunderstanding. But the code in this book is not well presented. It is VERY (!) blown up with low-quality doc-comments. On the other hand you get no explanatory text to tell you why things are made just so (remember: you are probably not yet an expert). You flip pages and pages in search for the flesh amongst the bones and you find neither flesh nor bones. The love and detail in the examples that I am used to from my other o'reilly books, is lacking here.
Attention: My comment aims for edition 3.1 of the book NOT for edition 3.0. The funny thing is that I chose to buy the book after having read some pages of edition 3.0 at 'google books' and 'paperc'. I liked version 3.0 and thought: why not just buy the newest edition? But somehow 3.1 is very different from 3.0, even part of the authors changed.
3 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
I'm writing this recension to emphasize what "franzb" already stated: This book does not manage to tie in with its predecessor.
While the choice of topics and the way the chapters are based on each other is beyond criticism, the overwhelming impression is that the book badly needs more reviews and clearer examples.
There are dozens of these little mistakes that confuse the reader and imply that proofreading was skipped, like this one:
- The chapter "transactions" builds upon some EJBs around blackjack. The appendix (30 pages really bad formatted source-code) states "our example is a transaction aware poker service".
- The chapter "interceptors" misses the WHOLE story behind EJB 3.1 (loosely decoupled interceptor bindings) and simply repeats the old EJB 3.0 version of hard code dependencies to interceptor bindings. That's definitely a major issues, because the book clearly doesn't hold what the title promises.
As a quintessence:
- This books covers interesting and complex topics in a often confusing way.
- Buy it if you need a quick update from 3.0 or just want to skim through some topics
- Think twice if you are new to EJB at all
Cheers,
Jan
While the choice of topics and the way the chapters are based on each other is beyond criticism, the overwhelming impression is that the book badly needs more reviews and clearer examples.
There are dozens of these little mistakes that confuse the reader and imply that proofreading was skipped, like this one:
- The chapter "transactions" builds upon some EJBs around blackjack. The appendix (30 pages really bad formatted source-code) states "our example is a transaction aware poker service".
- The chapter "interceptors" misses the WHOLE story behind EJB 3.1 (loosely decoupled interceptor bindings) and simply repeats the old EJB 3.0 version of hard code dependencies to interceptor bindings. That's definitely a major issues, because the book clearly doesn't hold what the title promises.
As a quintessence:
- This books covers interesting and complex topics in a often confusing way.
- Buy it if you need a quick update from 3.0 or just want to skim through some topics
- Think twice if you are new to EJB at all
Cheers,
Jan
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
7 Rezensionen
5 von 5 Kunden fanden die folgende Rezension hilfreich
Not a reliable source of information
21. August 2011
Format:Taschenbuch|Von Amazon bestätigter Kauf
Here is why i did not like this book:
* Code snippets alongside text (in many examples) do not exhibit the concept under discussion completely. This alone was a show-stopper for me. I (and i assume others) do not want to go through a 500 line example (in appendix or companion code) to understand a concept
* Coverage on session beans could have been more exhaustive
* Coverage on message driven beans is awesomely bad
* Coverage of "Queries, Criteria, JPA QL" does not cover Criteria API. Or wait a second, maybe it does cover it but without specifying the word "Criteria API" in the text, ever!
* Mistakes in code/xml at many places, looks like released in haste before a stringent review was done (I know that errata is there, but should ...)
* The text is not structured in an intuitive way. "A summary of topics to come at start and then going deep in each topic" is not followed. At times, one has to read through the full chapter to make out the possible ways of doing something by himself/herself
* Written by different authors clearly evident by their different writing style. Publisher should have facilitated (if not enforced) some uniformity to the content style
* Could have been under 450 page book. Putting all the code in appendix doesn't provide much value when the companion code is available, just makes the book more bulky (and costly?)
I will not recommend this book to anybody. It is saddening to see an O'Reilly book of this standard.
--Nafees
* Code snippets alongside text (in many examples) do not exhibit the concept under discussion completely. This alone was a show-stopper for me. I (and i assume others) do not want to go through a 500 line example (in appendix or companion code) to understand a concept
* Coverage on session beans could have been more exhaustive
* Coverage on message driven beans is awesomely bad
* Coverage of "Queries, Criteria, JPA QL" does not cover Criteria API. Or wait a second, maybe it does cover it but without specifying the word "Criteria API" in the text, ever!
* Mistakes in code/xml at many places, looks like released in haste before a stringent review was done (I know that errata is there, but should ...)
* The text is not structured in an intuitive way. "A summary of topics to come at start and then going deep in each topic" is not followed. At times, one has to read through the full chapter to make out the possible ways of doing something by himself/herself
* Written by different authors clearly evident by their different writing style. Publisher should have facilitated (if not enforced) some uniformity to the content style
* Could have been under 450 page book. Putting all the code in appendix doesn't provide much value when the companion code is available, just makes the book more bulky (and costly?)
I will not recommend this book to anybody. It is saddening to see an O'Reilly book of this standard.
--Nafees
2 von 2 Kunden fanden die folgende Rezension hilfreich
Pretty bad book
13. September 2011
Format:Taschenbuch|Von Amazon bestätigter Kauf
Only 400 pages out of 738 is real content, topics could be explained better and those wasted pages could be used for that instead of code samples... Criteria API is not even mentioned in Criteria API chapter!!! Now thats disrespectful to readers who paid for this book... Especially when Criteria is pretty big addition to JPA2. Anyway don't buy this book.
2 von 2 Kunden fanden die folgende Rezension hilfreich
Terrible companion codes to demonstrate the concepts
8. August 2011
Format:Taschenbuch
The first pom doesn't build at all, after going through much trouble to get to the source of its companion codes. That didn't inspire me to buy this book.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
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
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
