Project

General

Profile

Defect #696

WebClient compilation errors if the scripting language of the report is Groovy

Added by Andrei Costache almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Andrei Costache
Start date:
06/07/2013
Due date:
% Done:

100%

Estimated time:
Browser (if web client):

Description

The most straightforward way to reproduce is if you start the Developer's WebClient and you call runReport you get compilation errors, similar to https://www.servoyforge.net/issues/416.
Apparently if you start smart client first (and after a couple of runReport runs), web client works ok.

The current workaround for this is to compile the report/subreport files with the plugin's compileReport function before the runReport call.

History

#1

Updated by Andrei Costache almost 12 years ago

(this problem occurs only for foundset based reports and web client started from developer/appserver and for sql based reports and web clients started from the appserver)

#2

Updated by Andrei Costache almost 12 years ago

  • Status changed from New to Closed
  • Assignee set to Andrei Costache
  • % Done changed from 0 to 100

The best practice here is to use Java as scripting language.
The wiki has been updated accordingly (Foundset_Based_Reports_Guidelines).

Also available in: Atom PDF