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

Java or web service

Before adding a custom Java service to a project, ensure that a Java service is the best way to provide the desired functionality. A straight Java service may not be the best solution if you expect to reuse the functionality in other projects.

One option is to package the core functionality up into a JAR file. This makes it easier to reuse the functionality provisioned by a set of classes. Subsequent projects will still need to use a Java service; however, they don't need to recompile another copy of the Java sources. Instead, the JAR file is added to the classpath and the Java service class uses the classes of the JAR just like any other JAR file import. This can be a good option if your organization produces JAR files as artifacts from other projects. Simply take the output targets from those builds and bring them into the WaveMaker projects. The downside to this approach is that any updates to the classes in the JAR file must be propagated to each project using the...