<< 1 >>
Rating: 
Summary: Great introduction to JMS
Review: "JMS is a Java Application Programming Interface (API), which allows software applications, components, and objects to create, send, receive, and read messages". The author starts with an introduction to J2EE, and explains where JMS fit in this technology. Then he gives an introduction to message service, and finally the Java message service. The first three chapters introduce J2EE. EJB(the heart of Java Enterprise technology), session beans, entity beans, and how to reach a session bean and an entity bean as a web client are also discussed. The second section of the book (chapters 4, 5, 6) gives an introduction to message service, MOM, TPM, RPC, ORB.. And finally chapters 7, 8, 9, 10 and 11 discuss Java Message Service. Every section of the book is accompanied by examples and applications.
This book targets Java application developers. Although programming experience is assumed, the first 3 intro chapters will give you the details you need.
Rating:
Summary: Good intro to JMS and good for architecture understanding
Review: I am using this book in a JMS lunchtime brownbag group. I picked this book after browsing the JMS books that were in my local Borders bookstore and deciding that this book contained a good description of why you would use message queuing technology and why you shouldn't. I found this book EXCELLENT for explaining WHY all of the different features in JMS exist and providing some realistic (good) examples. I now feel comfortable with how to use the JMS features. Because I'm new to J2EE, I didn't want to try to use it in addition to learning JMS. I just wanted to use J2SE with JMS. To do this I downloaded SonicMQ's JMS provider and found SonicMQ's tutorial EXCELLENT for getting started quickly because it allowed me to use J2SE with JMS. SonicMQ gives you a JMS Client program that makes it easy to experiment with the different features of JMS using software that already works. I then modified sample JMS code that I wrote to join in topics and queues that SonicMQ had started. I'm now going to starting using J2EE as the book describes. Appendix A describes what to do to install and set up Sun's J2EE app/web server. I personally liked the discussion of J2EE as I am new to that technology and liked the "context" of how JMS fits into J2EE. As for the other reviewer's who bash this authors statements on some technical details. OK, I don't necessarily agree with all of the points the author makes, but it doesn't mean that the book is full of holes. In general I've found the book acurate or at least consistent with other books and articles I've read.
I'm sure the book isn't perfect but for me it has a good addition to my library. After purchasing the book (from Amazon's used books section for around $3 bucks) I've been real happy with the choice.
Rating:
Summary: Good intro to JMS and good for architecture understanding
Review: I am using this book in a JMS lunchtime brownbag group. I picked this book after browsing the JMS books that were in my local Borders bookstore and deciding that this book contained a good description of why you would use message queuing technology and why you shouldn't. I found this book EXCELLENT for explaining WHY all of the different features in JMS exist and providing some realistic (good) examples. I now feel comfortable with how to use the JMS features. Because I'm new to J2EE, I didn't want to try to use it in addition to learning JMS. I just wanted to use J2SE with JMS. To do this I downloaded SonicMQ's JMS provider and found SonicMQ's tutorial EXCELLENT for getting started quickly because it allowed me to use J2SE with JMS. SonicMQ gives you a JMS Client program that makes it easy to experiment with the different features of JMS using software that already works. I then modified sample JMS code that I wrote to join in topics and queues that SonicMQ had started. I'm now going to starting using J2EE as the book describes. Appendix A describes what to do to install and set up Sun's J2EE app/web server. I personally liked the discussion of J2EE as I am new to that technology and liked the "context" of how JMS fits into J2EE. As for the other reviewer's who bash this authors statements on some technical details. OK, I don't necessarily agree with all of the points the author makes, but it doesn't mean that the book is full of holes. In general I've found the book acurate or at least consistent with other books and articles I've read.
I'm sure the book isn't perfect but for me it has a good addition to my library. After purchasing the book (from Amazon's used books section for around $3 bucks) I've been real happy with the choice.
Rating: 
Summary: Wrong information regarding J2EE in general
Review: The book covers J2EE basic and JMS history in its three chapters. They all have a number of claims that I could not agree with. Take a look of these examples: "JDBC us a Java interface that resides between applications and databases, and can access any database. As a developer, you do not have to know database-specific issues. After a connection is made, all commands and implementations are the same for all databases." Forgetting differencies in SQL, for instance joins? "If I put business logic methods into a Java servlet instead an EJB, is it still an enterprise application? No. Even though a Java servlet resides on the server like an EJB, it still is part of presentation layer. In this case, it is called a two-tier model, and it is not distributed object model." This may be the reason why EJB is misused so often... (Mini-antipattern: Everything is an EBJ, from a very good book Bitter Java) "But I do not think you can have an enterprise application without a database." So application accessing legacy system via JMS is not an enterprise application? "Entity beans are used as database representations and serve session beans as an artificial database. This way, you will not increase database activity during heavy network traffic." Entity beans may cause a very bad performance. It causes a huge network traffic when entity beans loads the data from the database field by field. (Round-tripping antipattern, Bitter Java) "Most MOM products have additional services that do not exist in RPC or ORB products such as translating data, security, broadcasting, data to multiple applications, locating resources on the network, error recovery, better debugging, and so on." For instance, data translation, security, and locating resources exists in CORBA. I could continue the list of issues that I do not agree but I'll stop here.
Rating:
Summary: Wrong information regarding J2EE in general
Review: The book covers J2EE basic and JMS history in its three chapters. They all have a number of claims that I could not agree with. Take a look of these examples: "JDBC us a Java interface that resides between applications and databases, and can access any database. As a developer, you do not have to know database-specific issues. After a connection is made, all commands and implementations are the same for all databases." Forgetting differencies in SQL, for instance joins? "If I put business logic methods into a Java servlet instead an EJB, is it still an enterprise application? No. Even though a Java servlet resides on the server like an EJB, it still is part of presentation layer. In this case, it is called a two-tier model, and it is not distributed object model." This may be the reason why EJB is misused so often... (Mini-antipattern: Everything is an EBJ, from a very good book Bitter Java) "But I do not think you can have an enterprise application without a database." So application accessing legacy system via JMS is not an enterprise application? "Entity beans are used as database representations and serve session beans as an artificial database. This way, you will not increase database activity during heavy network traffic." Entity beans may cause a very bad performance. It causes a huge network traffic when entity beans loads the data from the database field by field. (Round-tripping antipattern, Bitter Java) "Most MOM products have additional services that do not exist in RPC or ORB products such as translating data, security, broadcasting, data to multiple applications, locating resources on the network, error recovery, better debugging, and so on." For instance, data translation, security, and locating resources exists in CORBA. I could continue the list of issues that I do not agree but I'll stop here.
Rating: 
Summary: Java Message Service (JMS) for J2EE
Review: This book is about understanding,
Message-oriented middleware(MOM),on which JMS is based.
As EJBs have very important role in JMS application, they have been covered with EJB examples.
Program JMS applications and increase their reliability.
Combine the strengths of XML and JMS using JAXP.
Use JMS with web client
Develop applications using he JMS API.
In this part of book language is so easy to understand. Block diagram,picture and web site for reference has been given whereever required for detail explanation.Later on they are started with basic to comlicated level of examples.And all possible code has been given.And all the code from this book is available on website in .zip format.
Using this book you will learn,Get a handle on EJB, JNDI, Middleware architecture and Java Message Service.And many more like require tool for XML,J2SE and J2EE Settings,
development and deployment tool and web server for J2EE application.
I recommend this book because of the detailed, up-to-date coverage of JMS and the depth of technology covered.
Rating: 
Summary: It is very helpful and great book for JMS beginners
Review: This is a great JMS introduction book. It is an excellent resource if you know Java 2 Standard Edition, and if you want to learn Java Message Service API, one of the key technologies of J2EE.
I worked on many software projects, and I used Java language and some Java technologies such as Java Applets on my projects. I needed to learn Java 2 Enterprise Edition and new J2EE APIs. This book introduced me not only to JMS but also J2EE. It provides brief information about J2EE and its key elements, session beans and entity beans, with detailed and well-designed examples. Having experience on these beans helps you understand message-driven beans, the key element of the JMS on J2EE applications.
The book even contains information on where to download necessary software, how to install them, and how to use them properly on your projects.
The book gives detailed information for JMS API with lots of examples. Another good feature of the book is that it provides information about JMS vendors in the market. The book compares them and helps you find the right package for your projects. This book does not focus on only Message-oriented issues. It covers almost everything on JMS-related issues from vendors to necessary software, from J2EE to history of message-oriented systems, from message-driven beans to web applications, and from XML to JMS reliability.
Chapters 4, 6, 9 and 11 are particularly useful for JMS beginners like me, even if you do not have enough experience on J2EE. Thanks for the book. It is well worth the money and very helpful for my projects.
Rating:
Summary: The worst ....
Review: Wow ... WOW! I have never had the misfortune to read such a terrible, terrible technical book. I am a technical specialist on JMS and have read the majority of available publications. This book is technically inacurate, has the most attrocious grammer (the author is Turkish and undoubetdly has a far superior grasp of English than I do of Turkish - buit the grammer patterns contained in the book are too reminiscent of Turkish). For example,
1st sentence, page 1, chapter 1 ... "This chapter provides basic information about the Java language and how common it is used in the computer world by software developers." My text has NO misprints and quotes exactly. The technical content is just as poor. The 1st 30% of the book attempts to cover Java and J2EE ... I bought this book to learn JMS, lets assume I know Java and J2EE ... Try this, "Middleware is defined as transportation software that transfers information from one application to one or more other software applications". I can't believe this book managed to be published and am astounded the editors let this past. ...
<< 1 >>
| 
