<< 1 >>
Review: Hmm, even one star does not do justice to this book. The first couple of chapters deal with .net and the other chapters deal with the fundamentals of j2ee. The coverage of each seems to be ok, but not to an extend that you can actually learn something from it. Just what i am saying, it is coverage for 2 times 6 or 7 chapters. E.g. the cover of the book mentions XML, in my opinion an integral part of j2ee. But hey, it is not mentioned in the J2EE section.
Then finally this book seems to discuss interoperability, and guess what, it does not. The last chapter discusses a commercial tool (who ownes the shares?) which should help you out. But is that the only way, or only solution for interoperability ?
In my case there is just nothing in the book that could help me out, so i gave it a one star
Summary: Nice coverage, little interoperability
Review: I was looking particularly forward to this book, in large part because I confused the author - Dwight Peltzer - with the talented Charles Petzold, author of the seminal Programming Windows. Hopefully others will not be similarly confused, because Peltzer lets his almost-namesake down.
The premise behind the book is that .NET and J2EE are two of the leading technologies being used for large systems today. This is true, and neither is "merely" a programming language but a complex suite of tools that offer many enterprise-grade facilities.
Rather than take a biased view that one is necessarily better than the other or "Microsoft is evil" and the like, Peltzer recognises that the real nuts-and-bolts I.T. worker needs to be up-to-speed on both platforms. Hence, the book takes a pragmatic approach and strives to explain how to make these two interoperate in a heterogeneous environment.
Alas, this explanation never occurs. The back cover blurb proudly states the book has been technically reviewed by both Microsoft and Sun and that it is a one-of-a-kind resource giving solutions to cross-platform communications. It asserts Peltzer examines many technical issues arising from integrating .NET and J2EE. But, sorry, I just don't see it - unless you count the penultimate chapter, a throw-away discussing third-party tools.
Instead, eight chapters go into detail about what .NET and J2EE are and aren't, and what they can do - by themselves. The last chapter even has some real "best-practice" suggestions. Yet, every single example is .NET talking to .NET, Java talking to Java - again, unless you count the brief coverage of third-party offerings.
To his credit, Peltzer does give more than just surface coverage of each technology and possibly a good programmer could make use of the information given to work out how to interoperate the languages (for instance, working directly with XML structures). Nevertheless, this isn't a book on .NET & J2EE interoperability; a better title would be ".NET & J2EE: A guide to each".
Summary: Great Explanation of the current 'State of the Art'
Review: With a goal to explain the current state of the technology and describe best-practice ways of working within and between both .NET and J2EE, Peltzer hits his mark. I recommend this book for individuals trying to identify the dizzying array of capabilities within each platform and how they might be connected. Peltzer examines two third-party technologies for providing interoperability that give a good foundation for the problems that must be overcome to facilitate communication between the platforms. It is the examination of these technologies, using the first two Parts of the book as reference that give the true benefit of the book: a whole-view understanding of J2EE and .NET and a pragmatic view of the challenges in bridging the interoperability gap.
<< 1 >>