- Series: Pragmatic Programmers
- Paperback: 260 pages
- Publisher: Pragmatic Bookshelf; 1 edition (July 3, 2009)
- Language: English
- ISBN-10: 1934356409
- ISBN-13: 978-1934356401
- Product Dimensions: 7.5 x 0.7 x 9 inches
- Shipping Weight: 1.2 pounds (View shipping rates and policies)
- Average Customer Review: 16 customer reviews
- Amazon Best Sellers Rank: #3,712,907 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Modular Java: Creating Flexible Applications with OSGi and Spring (Pragmatic Programmers) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
About the Author
Craig Walls is a professional software developer with over 15 years of experience in several industries, including telecommunications, finance, retail, and education. He's currently involved in the development of a natural language business intelligence tool with an Addison, TX-based company. He is the author of Spring in Action and XDoclet in Action (published by Manning) and is an avid proponent of Spring, open-source, and agile development.
Showing 1-7 of 16 reviews
There was a problem filtering reviews right now. Please try again later.
If you are going to use this book as a guide to how you approach the OSGi universe and you are not already a Maven user or a Spring user, you need at least a couple of books more and a lot of time to get you sorted. (You need at least a Maven book and possibly a Spring book if you are not already familiar with these technologies). If you are not already an experienced Maven user I suggest you stay away from this book. You are going to burn a lot of time learning Maven and figuring out all the OSGi annoyances the book doesn't cover.
The useful parts of the book that give you an introduction to OSGi are readable and probably and a good intro. But nothing more. The worthwhile parts of this book is a one-afternoon read.
When learning OSGi I found the specification documents of OSGi itself to be surprisingly well-written.
For the blantant misrepresentation of the book in the title of the book I would be tempted to give it a 1 star rating. I, as a reader was interested in OSGi. Not the baggage of the author.
I decided to give it two stars since the parts of the book that are actually about OSGi are a quick read and do give you an intro to OSGi -- though it is a weak two stars.
I find the style a bit wordy: "You're probably wondering how I knew what the group and artifact IDs should be. Well, it certainly would be nice if there were some sort of search engine that would find these things for us. But since nobody has developed one of those yet..." p. 59
I appreciate a friendly style, but this can be a lot to wade through.
The book could be improved with better introductions that layout the chapter in high-level terms. As it is, you have to walk the path with the author to get an idea of what the chapter is about. It really is more of a workbook that way.
OSGI has many popular implementations and this presents a problem for the author of an OSGI book: which implementation to use? Writing for all, or a substantial subset would be quite a task. In some cases Walls writes examples for three, in others just one. I don't know if some of the problems I see stem from using a different implementation, or from a generic error. The OSGI implementation used is another variable to consider when something doesn't work. A 5 star book would have tested the code across a number of implementations and flagged differences in each example.
Having said that, I'm glad the book was written and don't have suggestions for other, better books. Though obvious [...] makes for a good start.
I've found an error in the published material approximately every 10 pages. In fact if you typed all the code in the book line for line NONE of it would work. There are good ideas and concepts in material, but the lessons will come at great expense to your personal time. The author inconsiderately uses you and your money as his personal Quality Assurance. Buy something else from a more thoughtful author who prides himself on the quality of his work.
P.S. - The book is maven and pax-construct heavy. Be prepared for baptismal by fire if you think your Ant background will suffice.
- OSGi 101
- No popular IDE coverage
- Solely reliant on PAX (which isn't that good)
- No real depth into OSGi