Your one-stop resource for .NET and J2EE interoperability
Achieve integration between the platform-independent technologies J2EE and .NET. Technically reviewed by both Microsoft and Sun technologists, this one-of-a-kind resource provides solutions to cross-platform communications between business partners and the transmission of mission-critical enterprise data. Using a case study to provide a framework, computer science professor Dwight Peltzer examines the many technical issues arising from integrating J2EE and .NET, offering practical solutions, advice, and best practices that can be put to use by working IT professionals and developers. Packed with explanations of each technologyand how they work togetherthis focused resource will help you successfully integrate J2EE and .NET technologies.
About the Author: Dwight Peltzer is a well-known author, consultant, and lecturer on Java-based J2EE technologies, the .NET Framework, and the Microsoft suite of server products.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
4 of 4 people found the following review helpful:
1.0 out of 5 stars
interoperability,
By friso "friso" (netherlands) - See all my reviews
This review is from: .NET & J2EE Interoperability (Paperback)
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
3.0 out of 5 stars
Bored to tears,
By Yuri Krasnov (San Francisco, CA) - See all my reviews
This review is from: .NET & J2EE Interoperability (Paperback)
This book discusses on .NET and J2EE basics and more of their integration options than interoperability. It does'nt make sense to call it as interoperability, in one of the chapters the author suggests to use a COTS interface to enable right terms is integration than interoperability. No question, The book is well-written with good explanation of concepts but the book lacks practical examples. And it is also boring to choose only SOAP/XML Web services for everything. If that is the only option then we need to live with it.
3.0 out of 5 stars
Nice coverage, little interoperability,
By
This review is from: .NET & J2EE Interoperability (Paperback)
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".
Share your thoughts with other customers: Create your own review
|
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|