What I investigated in Wagby development Note 1

Introduction

I used Wagby at work and there wasn't much information, so I thought I'd write it. I would like to describe what I was investigating and resolved.

What is Wagby

Please refer to the post below. Wagby Overview

My environment

OS:Windows10 Wagby:8.2.0

Where can I customize it?

javascript --Front of each screen (works with browser) ――You can write freely --DOM manipulation, event processing, etc. --The dojo Toolkit framework is adopted as standard, and life cycle events such as onload need to be adapted to the framework. --Server side --Called by Java running on the server --Called only at a specific timing (cannot be executed at any timing) -Work on Nashorn

Java --Java automatically generated by wagby --Inherit and rewrite processing --wagby Standard non-automatically generated classes are not used even if inherited ones are created ――Maintenance seems to be troublesome --Java created completely independently --You can create your own Util class and call it arbitrarily.

JSP --Elements can be added ――Maintenance seems to be troublesome

CSS --You can write your own format, but not the basics --May be written when the standard format is not enough

Impressions

Basically, customization other than javascript seems to be troublesome at the time of version upgrade.

If you customize too much, javascript will be difficult

Front customization requires getting used to the dojo toolkit

Please note that Nashorn of Java 8 does not support es6

** I want a list of standard APIs. ** **