Book Image

Easy Web Development with WaveMaker

By : Edward Callahan
Book Image

Easy Web Development with WaveMaker

By: Edward Callahan

Overview of this book

Developers of all levels can now easily develop custom, responsive, and rich web application clients with secure, scalable servers utilizing relational databases and RESTful services using WaveMaker Studio. Whether you need a departmental business application or a form application for your weekend club, this book will show you how to design, develop, and deploy professional grade web applications with WaveMaker. Easy Web Development with WaveMaker will help you use WaveMaker to design, develop, and deploy rich, responsive web applications, even if you are not a programmer. If you need to build a data-driven web application, but you only know ‘enough to be dangerous,' you need this book. This book examines every angle of using WaveMaker to build applications, from dissecting examples to customizing, deploying, and debugging your own applications. This book enables the non-professional programmer to become comfortable not only with using WaveMaker Studio itself, but also with the artefacts produced by the studio as well as the runtime and services provided by the WaveMaker framework. You will learn everything, from how customize the user experience with JavaScript and CSS to integrating with custom Java services and the Spring Framework server-side. Easy Web Development with WaveMaker 6.5 is packed with examples, code samples, screenshots, and links to equip you to be successful with WaveMaker Studio.
Table of Contents (23 chapters)
Easy Web Development with WaveMaker
About the Author
About the Reviewers
Styling the Application
Working with Databases
Utilizing Web Services


The built-in logger should be used over System.out at all times. Examples of using the log function are included in the sample service operation added to each newly minted service class. If you use the default extension of JavaServiceSuperClass, logging is already set up for you, and all you need to do is use log() with a log level instead of System.out.println().

Good logging is critical to supporting and debugging any Java service. The JavaServiceSuperClass class makes using the logging subsystem so easy there is no good reason to use System.out.println ; System.out simply lacks the controls of log. Using the logger with levels allows you to control the verbosity of logging using /src/ instead of recompiling sources.

For example, in our updateCustomer() example function, we use INFO to log the name of the company being updated:

log(INFO, "Updating customer: " + customer.getCompany());

But, if there is an exception in performing the update, we use ERROR to log the condition...