Although there are some issues with Java EE 6 Development with NetBeans 7, they tend to be very minor and are not overly distracting. Nothing is perfect and no book is perfect. There is some discussion of how memory leaks can occur in Java, a principle worth understanding whether working on standard or enterprise Java applications. Appendix B is a relatively short appendix, but it does give an overview of the types of information that NetBeans 7 provides that can be used to identify performance issues. The final portion of Java EE 6 Development with NetBeans 7 is an appendix focused on profiling with NetBeans 7. For example, the steps of setting breakpoints, stepping over, stepping into, and using the Local Variables window are the same as for standard applications.Īppendix B: Identifying Performance Issues with the NetBeans Profiler The example is intentionally broken so that debugging effort is needed and the example is based on Java EE technologies JSF, CDI, and JPA.įortunately for developers familiar with using NetBeans for debugging standard Java applications, the process for debugging enterprise Java applications is very similar. Another piece of the NetBeans 7 debugging coverage that is specific to Java EE is the example itself. The chapter describes using NetBeans 7 with the embedded GlassFish instance to essentially boil initial enterprise debugging steps down to a single step. For the most part, the coverage of both debugging and profiling in NetBeans 7 is largely applicable to any Java development, enterprise or standard.Īppendix A covers debugging with NetBeans 7 and does provide some information specific to debugging Java EE applications. The reason for this is that I was curious regarding what the author had to say regarding debugging and profiling in NetBeans 7. I'm not normally the type of reader to "skip to the end," but I must admit that I read the Appendices first in this case. This makes it easy for NetBeans 7 to create methods for handling both XML and JSON.Īppendix A: Debugging Enterprise Applications with the NetBeans Debugger I thought it was interesting, albeit not surprising, that the client API used for the generated client is Jersey's Client API. The discussion includes details of what NetBeans does to make this happen, including the use of JPA facsdes and the typical use of Jersey.Īs was done for coverage of NetBeans 7 with JAX-WS, this chapter demonstrates how to use NetBeans 7 to test a newly created REST-based web service and how to use NetBeans 7 to generate a client of the REST-based web service. Heffelfinger begins his coverage of Java EE 6/JAX-RS support in NetBeans 7 with a discussion on and demonstration of generating a REST-based web service from an existing database. It is nice to see a chapter of Java EE 6 Development with NetBeans 7 devoted to JAX-RS and REST in Java EE 6 with NetBeans. I have blogged on REST and on JAX-RS before and really like much about both. One of the most exciting additions to Java EE 6 is that of JAX-RS to support RESTful web services. This is demonstrated in this chapter via an example that shows generation of Java classes with stub methods based on a provided existing WSDL.Ĭhapter 11: RESTful Web Services with JAX-RS There are many who argue that contract-based, top-down web service design is the preferred approach. One of these examples demonstrates this by creating the EJB in conjunction with creation of a web service and the other of these examples demonstrates this by creating a web service on an existing EJB. The second example and third example use JAX-WS to expose a stateless session EJB as a web service. He provides an example of generating a simple length conversion web service using NetBeans 7's wizard, changing the body of the generated methods on the properly annotated Java POJO, and automatically generating WSDL and a client to test the simple web service. Heffelfinger opens up his discussion on NetBeans 7 support for SOAP-based web services by introducing WSDL and by discussing how NetBeans 7 allows for either top-down (contact first with Java generated from existing WSDL) or bottom-up (WSDL generated from existing Java classes) development of SOAP-based web services. There are many areas of Java EE 6 where this is true, but it is no more true than in the area of SOAP-based web services and JAX-WS. A common theme in Java EE 6 Development with NetBeans 7 is that of using NetBeans 7 to reduce the boilerplate code a developer needs to write. I cannot think of a better candidate for the need of good tools to help with development than the SOAP-based web service. Chapter 10 covers the general principle of a web service (whether SOAP-based or REST-based) before focusing exclusively on SOAP-based web services (REST is covered in the next chapter).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |