- Taschenbuch: 444 Seiten
- Verlag: Manning; Auflage: illustrated edition (3. März 2005)
- Sprache: Englisch
- ISBN-10: 1932394354
- ISBN-13: 978-1932394351
- Größe und/oder Gewicht: 23,4 x 18,5 x 3 cm
- Durchschnittliche Kundenbewertung: 4.0 von 5 Sternen Alle Rezensionen anzeigen (2 Kundenrezensionen)
- Amazon Bestseller-Rang: Nr. 155.155 in Englische Bücher (Siehe Top 100 in Englische Bücher)
|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
| ||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt Spring in Action. gegen einen Amazon-Gutschein in Höhe von EUR 0,25 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. |
|
Dieses Buch gibt es in einer neuen Auflage:
|
Produktinformation |
Produktbeschreibungen
Kurzbeschreibung
A guide to the lightweight container framework that presents an exciting alternative to EJB J2EE offers Java developers a very powerful enterprise framework. But portions of J2EE can be complicated--specifically Enterprise JavaBeans. By shouldering the burden of J2EE's complexities and providing the developer with a much simple abstraction, Spring makes developing J2EE application significantly simpler. It also provides a viable alternative to EJB, providing many of the same features offered by EJB, but without EJB's complexities. Written for enterprise Java developers who have become disillusioned with the complexity and bulk involved with EJB development, "Spring in Action" demonstrates how the Spring framework can make coupled code easy to manage, understand, reuse, and unit-test. Spring's employment of inversion control and aspect-oriented programming techniques to encourage loosely coupled code is explained, providing programmers with the ability to use JavaBeans with the power and enterprise services only previously available in the heavier Enterprise JavaBeans. Even hard-core EJB fanatics may find some value in this book as the next specification of EJB will more closely resemble Spring than the current EJB specification. Software architects will find Spring in Action valuable in assessing and applying the lightweight techniques prescribed by Spring.
Synopsis
A guide to the lightweight container framework that presents an exciting alternative to EJB J2EE offers Java developers a very powerful enterprise framework. But portions of J2EE can be complicated--specifically Enterprise JavaBeans. By shouldering the burden of J2EE's complexities and providing the developer with a much simple abstraction, Spring makes developing J2EE application significantly simpler. It also provides a viable alternative to EJB, providing many of the same features offered by EJB, but without EJB's complexities. Written for enterprise Java developers who have become disillusioned with the complexity and bulk involved with EJB development, "Spring in Action" demonstrates how the Spring framework can make coupled code easy to manage, understand, reuse, and unit-test. Spring's employment of inversion control and aspect-oriented programming techniques to encourage loosely coupled code is explained, providing programmers with the ability to use JavaBeans with the power and enterprise services only previously available in the heavier Enterprise JavaBeans.Even hard-core EJB fanatics may find some value in this book as the next specification of EJB will more closely resemble Spring than the current EJB specification. Software architects will find Spring in Action valuable in assessing and applying the lightweight techniques prescribed by Spring.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
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).
|
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
7 von 9 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Für Leute die noch nichts mit Spring angefangen haben ist das Buch ein guter Einstieg. Die Theorie des Frameworks wird sehr schön einfach in guten Beispielen beigebracht.
Leider wird der Inhalt schnell zu knapp, wenn man anfängt etwas praktisch zu erreichen. Das heisst wieder googlen...
Für den Preis ist eine gute Investition, aber leider nicht ausreichend.
Leider wird der Inhalt schnell zu knapp, wenn man anfängt etwas praktisch zu erreichen. Das heisst wieder googlen...
Für den Preis ist eine gute Investition, aber leider nicht ausreichend.
22 von 51 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Wir haben vor kurzem das Spring-Framework in unserer Entwicklungsabteilung eingeführt. Deshalb haben wir einige Bücher zu diesem Thema gekauft, um einen schnellen Einstieg in die Materie zu bekommen.
Im Vergleich zu den anderen Büchern hat uns Spring In Action vor allem durch seine Einfachheit und Praxisnähe überzeugt. Wer in Spring einsteigt, will unserer Meinung nach nicht gleich durch Detailinfos erschlagen werden. Er/Sie sucht einfach nur die leicht verständliche Antwort auf alle Fragen, die sich im Laufe des Lernens und der ersten Entwicklungen stellen.
Damit ist Lucene In Action aus unserer Sicht zur Zeit das absolut beste Buch für Einsteiger in diese Thematik. Es vermittelt alles Wichtige und ist dabei auch noch sehr angenehm zu lesen.
Wer Profi-Tipps und weiterführendes Wissen sucht, ist dann gut vorbereitet, um dickere Wälzer oder das Internet auf der Suche nach Detailinfos zu durchforsten.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
36 Rezensionen
93 von 101 Kunden fanden die folgende Rezension hilfreich
Spring into action with Spring in Action
17. März 2005
Format:Taschenbuch
Information on the web about Spring can be found if you searched enough. The problem is that there was never any kind of clear guide and process by which you could either learn or make good use of the features in Spring.
I spent the better part of 2 hours last weekend at the bookstore reading through some chapters of Spring in Action and Spring PRO. I had already looked at Spring Live and was just too fond of it. Spring PRO turned out to be as dry a reading as the paper it's printed on. Sure it's got a lot of information, but geez, who needs that much, and who can read all of it when it's so hard to stay awake during the reading?
Spring Live offered something the other books didn't:
1- It's easy to read. The Authors, Craig Walls and Ryan Breidenbach, have a pretty good sense of humor, and has obviously put great effort in using good examples which everyone can understand. If you don't know how a student class registration works, you probably didn't go to school. I could have done without the Knight and singing what ever examples, but hey, they didn't hurt anything and got the message through.
2- The book flows in the natural way one would expect to work with Spring. I like the sequence of chapters, as Craig and Ryan layed them out. They start with a quick yet fairly thorough Spring startup, and run from there into wiring, AOP, dao and on down to complete the project. it just works and makes sense, and I don't feel like I'm left wondering about something. They always seem to get to what you need to know as you think about it.
While SiA didn't have the depth of Spring Pro, it still covered everything and then some, with accuracy with what you need to know. It's written from the standpoint, at least in my opinion, that you're a smart engineer, this is not your first time looking at Java or a framework, so they tell you what's going on, and let you figure out things further if you want to and when you need to. You're not plastered with a bazillion pages of details, leaving you skimming page after page for what you want to know. Spring Live just lacks in details, and seems more driven towards those who want to integrate Spring with other frameworks like Struts, and just seems a little too happy on self promoting the author's own tools.
I don't know what these stupid low rated reviews are talking about, it seems they were posted before the book was even published. Sad.
If you want to get going with Spring the right way, get this book and don't waste your money and time on anything else.
Hope this helps.
R
I spent the better part of 2 hours last weekend at the bookstore reading through some chapters of Spring in Action and Spring PRO. I had already looked at Spring Live and was just too fond of it. Spring PRO turned out to be as dry a reading as the paper it's printed on. Sure it's got a lot of information, but geez, who needs that much, and who can read all of it when it's so hard to stay awake during the reading?
Spring Live offered something the other books didn't:
1- It's easy to read. The Authors, Craig Walls and Ryan Breidenbach, have a pretty good sense of humor, and has obviously put great effort in using good examples which everyone can understand. If you don't know how a student class registration works, you probably didn't go to school. I could have done without the Knight and singing what ever examples, but hey, they didn't hurt anything and got the message through.
2- The book flows in the natural way one would expect to work with Spring. I like the sequence of chapters, as Craig and Ryan layed them out. They start with a quick yet fairly thorough Spring startup, and run from there into wiring, AOP, dao and on down to complete the project. it just works and makes sense, and I don't feel like I'm left wondering about something. They always seem to get to what you need to know as you think about it.
While SiA didn't have the depth of Spring Pro, it still covered everything and then some, with accuracy with what you need to know. It's written from the standpoint, at least in my opinion, that you're a smart engineer, this is not your first time looking at Java or a framework, so they tell you what's going on, and let you figure out things further if you want to and when you need to. You're not plastered with a bazillion pages of details, leaving you skimming page after page for what you want to know. Spring Live just lacks in details, and seems more driven towards those who want to integrate Spring with other frameworks like Struts, and just seems a little too happy on self promoting the author's own tools.
I don't know what these stupid low rated reviews are talking about, it seems they were posted before the book was even published. Sad.
If you want to get going with Spring the right way, get this book and don't waste your money and time on anything else.
Hope this helps.
R
41 von 46 Kunden fanden die folgende Rezension hilfreich
Excellent coverage and an easy read
9. März 2005
Format:Taschenbuch
There's been a bit of a rush of books about the Spring Framework recently with a number of publishers releasing their own titles one after another. Without having read those other books, I feel confident in saying "Spring in Action" won't let you down. It's a wonderful introduction to the framework and a handy reference for those desperate moments with the Spring configuration files.
What I especially like about "Spring in Action" is the style of writing. The book is largely about how to configure this and that and still I read most of the book in one sitting. The text flows well and the humor sprinkled throughout adds a nice touch. The other good things about this book include a good coverage of the Spring Framework itself. Only some parts of the Acegi security framework have been left out, as far as I can tell, and those features (ACL's and run-as) are not what I'd call essential so it didn't bother me much. In addition, the authors give a good comparison (brief, but a good overview) of Spring and other technologies and frameworks such as EJB, Struts, WebWork, Tapestry, PicoContainer, HiveMind, etc. Furthermore, the authors show you how to integrate with these other frameworks (except for the other IoC containers) and view technologies like JSP, JSF, Velocity and FreeMarker. Add to that, the index looks very comprehensive which is an important detail for a book that one might use as a reference afterwards.
So, what separates this book from perfection? For one it had a lot of little typos, the text did exhibit a bit of repeat (didn't I just read this sentence on the previous page?) here and there, and I feel like mixing multiple ViewResolvers was covered too lightly. I don't consider these to be big issues, though, and I won't hesitate for a second in recommending "Spring in Action" for someone looking to get started with the framework.
What I especially like about "Spring in Action" is the style of writing. The book is largely about how to configure this and that and still I read most of the book in one sitting. The text flows well and the humor sprinkled throughout adds a nice touch. The other good things about this book include a good coverage of the Spring Framework itself. Only some parts of the Acegi security framework have been left out, as far as I can tell, and those features (ACL's and run-as) are not what I'd call essential so it didn't bother me much. In addition, the authors give a good comparison (brief, but a good overview) of Spring and other technologies and frameworks such as EJB, Struts, WebWork, Tapestry, PicoContainer, HiveMind, etc. Furthermore, the authors show you how to integrate with these other frameworks (except for the other IoC containers) and view technologies like JSP, JSF, Velocity and FreeMarker. Add to that, the index looks very comprehensive which is an important detail for a book that one might use as a reference afterwards.
So, what separates this book from perfection? For one it had a lot of little typos, the text did exhibit a bit of repeat (didn't I just read this sentence on the previous page?) here and there, and I feel like mixing multiple ViewResolvers was covered too lightly. I don't consider these to be big issues, though, and I won't hesitate for a second in recommending "Spring in Action" for someone looking to get started with the framework.
49 von 57 Kunden fanden die folgende Rezension hilfreich
Good style: grade B+, Execution: D-
11. Dezember 2005
Format:Taschenbuch|Von Amazon bestätigter Kauf
This is a tough review to write because I felt the authors made a good effort in the writing of the book and explanations of the Spring Framework. Writing a book is no small feat, and technical books are a special beast.
With that last statement in mind, this is were the book sadly falls short. For one, the source code available online is a significant rewrite of the books' code. The authors explain ( on the publisher site ) that this is because they learned better ways and techniques to implement the samlpe application after the book went to print.
While improvement is always good, this presents two problems. 1. The sample application is now out of sync with the material. Not a good thing for those trying to learn, as you require more effort to study in tandem with the book. Also, and this is not to disparage the authors skill, but I buy books because I am expecting experienced, if not expert advice. If a small, sample application needs rewriting, perhaps they should write about something else?
Further down this road, the sample application has errors that prevent it from compiling. I suspect that the final build file was not tested, or it was a case of "well, it compiles on my machine". There were several dependencies that required changes to the build file so it could be compiled. Thankfully, I use Eclipse and imported the project. Eclipse immediately informed me of missing dependencies, which I resolved by getting those jars on the build path and in the build file so they would be deployed in the war archive. Examples are:
jakarta-commons/collections, and several core Spring jars relating to DAO and database access.
For an experienced developer, familiar with ant and a good IDE, it was not a lot of trouble to get it running, it just did not give me a good impression.
Bonus info for anyone switching the database out to postgresql: First, no matter what DB you swap in, you'll need to change a few hard coded references in the build file. I made property variables which I placed in build.properties. Then you will need to change the class User to something else ( and of course anything in the app that references it. ). Another great reason to use Eclipse.
Why you must change it, is User is a reserved keyword in postgresql and you will get databases errors because you can't name a table User.
With that last statement in mind, this is were the book sadly falls short. For one, the source code available online is a significant rewrite of the books' code. The authors explain ( on the publisher site ) that this is because they learned better ways and techniques to implement the samlpe application after the book went to print.
While improvement is always good, this presents two problems. 1. The sample application is now out of sync with the material. Not a good thing for those trying to learn, as you require more effort to study in tandem with the book. Also, and this is not to disparage the authors skill, but I buy books because I am expecting experienced, if not expert advice. If a small, sample application needs rewriting, perhaps they should write about something else?
Further down this road, the sample application has errors that prevent it from compiling. I suspect that the final build file was not tested, or it was a case of "well, it compiles on my machine". There were several dependencies that required changes to the build file so it could be compiled. Thankfully, I use Eclipse and imported the project. Eclipse immediately informed me of missing dependencies, which I resolved by getting those jars on the build path and in the build file so they would be deployed in the war archive. Examples are:
jakarta-commons/collections, and several core Spring jars relating to DAO and database access.
For an experienced developer, familiar with ant and a good IDE, it was not a lot of trouble to get it running, it just did not give me a good impression.
Bonus info for anyone switching the database out to postgresql: First, no matter what DB you swap in, you'll need to change a few hard coded references in the build file. I made property variables which I placed in build.properties. Then you will need to change the class User to something else ( and of course anything in the app that references it. ). Another great reason to use Eclipse.
Why you must change it, is User is a reserved keyword in postgresql and you will get databases errors because you can't name a table User.
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?
|
