0

I would like to see what is happening behind the scenes when the engine transforms XML file with screen definition into Groovy (I suppose) script. So that I can see the definition turning into more readable script, hopefully.

Where shall I place the breakpoint while debugging?

mrovnanik
  • 123
  • 9

2 Answers2

0

XML Screens are not transformed into scripts like XML Actions are. XML Screens and Forms are transformed by FreeMarker macros into the desired output text (html, xsl-fo, csv, etc). These macros are defined in the DefaultScreenMacros.html.ftl file for html output, and similarly named files (in the runtime/template/screen-macro directory) for other types of output.

David E. Jones
  • 1,721
  • 1
  • 9
  • 8
  • OK, I understand your answer in a way, that it is not a good idea to get deeper through debugger. A small progress, but still at least there is some. – mrovnanik Jun 02 '16 at 13:16
0

Also, in Tools (/apps/tools/Service) if you click on 'Service detail' you get a nicely rendered view of the generated groovy for any of your services called from screens (or otherwise called). 'Services' are a very intuitive unit for debugging in moqui.

Ronan Keane
  • 189
  • 8
  • This was a good one. The tool is really useful. I am not quite sure I understand what exactly being 'very intuitive unit for debugging' means. But, neveretheless, you really helped me out. – mrovnanik Jun 03 '16 at 21:07