I will explain the description of the specification changed in R7.10 and how to restore the change.

In R 7.10, handling in the case where the group display method is not specified in the screen layout has changed.[More ...]

R7.10 or earlier After R7.10
The first layout name is surrounded by a square regardless of how the group is displayed. For the first layout name, designation of the group display method is also effective.

This change will change the automatically generated JSP file.

Revert to old behavior

I will explain how to return to the old behavior.

  1. Open wagbydesigner/webapps/wagbydesigner/WEB-INF/classes/gencompatibility.properties with a text editor.
  2. Find the next entry.
    #jp.jasminesoft.jfc.gen.JspBodyGenerator_show.displayHiddenLayoutAsEmptyFrame=true
    
  3. Exclude # at the beginning of this line.
    jp.jasminesoft.jfc.gen.JspBodyGenerator_show.displayHiddenLayoutAsEmptyFrame=true
    
  4. Save this file.
  5. I will do a full build.

From R7.10, the file type item in the change history function was changed so that only the real file name is recorded in the change history log.We will explain how to return this to the old method (relative path notation starting from upload_dir).

  1. If the built Wagby application is running, stop it once.
  2. Open the webapps/wagby/WEB-INF/classes/jfcbase.properties file in the built wagbyapp folder with a text editor.
  3. Comment out the following line.
    jp.jasminesoft.jfc.app.PresentationPHelper.diff.getFileNameWithoutDirectory=true
    具体的には、先頭にセミコロン (;) を付与します。
    ;jp.jasminesoft.jfc.app.PresentationPHelper.diff.getFileNameWithoutDirectory=true
  4. Save the file and start the Wagby application.Please check the operation of change history.

After confirming the operation, apply the same change also to bin/webpage/WEB-INF/src/jfcbase.properties in the wagbydesigner folder.It will be reflected in the next build process.

Please carry out the same change processing every time Wagby upgrade is done.

In Wagby there are two dimensions, there is a function to minorize with the first dimension unit.So far, we implemented implementation using XSLT's count and sum functions, but this process had a problem of performance degradation as data to be summarized increased.

From R7.10, I made a calculation beforehand internally instead of XSLT.This improves performance.

Revert to old behavior

I will explain how to return to the old behavior.

  1. Open wagbydesigner/webapps/wagbydesigner/WEB-INF/classes/gencompatibility.properties with a text editor.
  2. Find the next entry.
    jp.jasminesoft.jfc.gen.XslGenerator_showTotal2.useCache=true
    
  3. We give # to the beginning of this line.
    #jp.jasminesoft.jfc.gen.XslGenerator_showTotal2.useCache=true
    
  4. Save this file.
  5. I will do a full build.

Effect of HSQLDB update

HSQLDB has been updated from 2.0.0 to 2.3.4.Because of that influence, the return value of SELECT COUNT () was Integer, but this has been changed to BigInteger.

Both are implementation classes of the java.lang.Number interface, but care must be taken when using the strict equality operator (===) in JavaScript.

Even if it has the same 0 value in the strict equality operator, Integer and BigInteger will not be judged as equivalent because they are of different types. Numbers written in the script are specifications that Nashorn automatically interprets as java.lang.Double, java.lang.Long or java.lang.Integer object. https://docs.oracle.com/javase/jp/8/docs/technotes/guides/scripting/nashorn/api.html#sthref22

For this reason, the following code written in the script affects.

var recordCount = session.createSQLQuery(
   "SELECT COUNT(*) FROM \"model1\" WHERE \"pkey\" = " + pkey).uniqueResult();
if ( recordCount === 0 ) {
...

Since "0" of "if (recordCount === 0) {" was interpreted as Integer on Nashorn side, in HSQLDB 2.0.0, return value of SELECT COUNT (*) is the same Integer, and it is exact equality operator It worked well, but in HSQLDB 2.3.4 it becomes a comparison between Integer and BigInteger and it will not be judged as equivalent.

How to respond

Comparison with numbers can be avoided by not using the exact equivalence operator.

if ( recordCount == 0 ) {

Abolition of BaseAction

The BaseAction class has been abolished in R7.10.This class is dependent on Struts.If you used BaseAction directly with the customization code, please rewrite according to the following procedure.

BaseAction.getCsvEncoding()

The JfcConfig class is substituted.Please use the following code.

p.appctx.getBean(jp.jasminesoft.jfc.service.JfcConfig.class).getCsvEncoding()

BaseAction.getJspEncoding()

The JfcConfig class is substituted.Please use the following code.

p.appctx.getBean(jp.jasminesoft.jfc.service.JfcConfig.class).getJspEncoding()

BaseAction.isDeniedNullForwardRequestName

The constants prepared for BaseAction are managed by the BaseController class.

jp.jasminesoft.jfc.controller.BaseController.isDeniedNullForwardRequestName

Change job definition

When "Batch Processing> Registering Your Own Classes in the Job Scheduler" is performed, a change occurs in the bean definition file registered in applicationContext.The org.springframework.scheduling.quartz.JobDetailBean class has been deprecated as the Spring Framework version has been updated from 3 to 4.Instead, specify org.springframework.scheduling.quartz.JobDetailFactoryBean class.[More ...]