[JAVA] Wagby Overview

Purpose

Since I had the opportunity to touch Wagby, I will briefly write an overview and usability

What is Wagby

Java-based ultra-fast development tool (Developer: [Jasmine Soft] [1]) [1]:https://www.jasminesoft.co.jp/ Basic development is done via Wagby Designer running on a web browser (Google Chrome). The contents have the above structure, and the automatically generated code does not have a special structure, so if you can understand the Java code, you can decipher it without problems. You can also use an IDE such as Eclipse for customization described later. (There are notes)

Basically, it is easy to create applications developed by Wagby that are suitable for core systems such as inventory management and customer management systems.

The basic flow of development is

Define model definition (table in DB) on Wagby Designer → Build

that's all

This is not to say, but if you have a simple inventory management system, you can actually develop it in the above one step. When you define a model, the search screen, list screen, detail screen, etc. are automatically generated, and if you specify the reference structure between models, it will be done automatically. You can easily link with an external DB by placing the JDBC driver in an appropriate location and setting it on the Designer side.

Customize

For fine adjustment and cooperation with external applications, you have to play with the automatically generated source code. The range that can be customized is quite wide, except for HTML, JS, CSS, Java logon and authentication. Customization can be applied by overwriting the automatically generated code, or by inheriting the class you want to customize, placing each in an appropriate folder, and building again.

The above points are mentioned here, but build errors and operation errors may occur frequently when customizing. For some reason, restarting Eclipse before building makes it less likely to cause an error, perhaps because it doesn't work well with Eclipse.

problem

There are some problems on the Wagby side, such as minor bugs and inability to deal with the specifications, but in the large part, we have the necessary and sufficient ability for application development. Rather, it is often the case in application development, but it is important to think about the system and DB configuration suitable for Wagby development.

Also, if you do not customize at all, the SQL statement actually issued is almost not optimized, so it may cause a performance problem (unverified).

Summary

The degree of perfection is high, but I have to think about the structure of the system to be built. I'm addicted to Dotsubo