#tablizer($dataset, "datasetTable") in Velocity-not working

Classic Servoy
1

Hi,

I am new to velocity reports. I tried the example in http://www.servoyforge.net/projects/vel … inOverview.
But the #tablizer does not work.

I want to display the dataset from databaseManager.getDataSetByQuery() function. How do I display it in Velocity?

2

Hi Erik,

maybe you could post on the VelocityReport ServoyForge forum?

As for #tablizer, there are a few things to check:
1/ did you declare the location of your reports folder in the Servoy admin plugins page? The “velocityreport.reportfolder” property should point to the (valid) location of a folder that holds your reports (on the server-side) - if not provided, it will try to use the Java System property ‘user.dir’ (where user will be the user that launched the Servoy server, either by the command line or service/daemon)
2/ in the folder declared with the “velocityreport.reportfolder” server property, you should have a file named “VM_global_library.vm” which is where the #tablizer macro is declared

If all is well, there might be a problem with the data, in which case, you could have a look at the servoy_log.txt and the velocity.log (that will be located next to it) to see if an exception has been throwed.

Hope this helps,

3

ptalbot:
Hi Erik,

maybe you could post on the VelocityReport ServoyForge forum?

As for #tablizer, there are a few things to check:
1/ did you declare the location of your reports folder in the Servoy admin plugins page? The “velocityreport.reportfolder” property should point to the (valid) location of a folder that holds your reports (on the server-side) - if not provided, it will try to use the Java System property ‘user.dir’ (where user will be the user that launched the Servoy server, either by the command line or service/daemon)
2/ in the folder declared with the “velocityreport.reportfolder” server property, you should have a file named “VM_global_library.vm” which is where the #tablizer macro is declared

If all is well, there might be a problem with the data, in which case, you could have a look at the servoy_log.txt and the velocity.log (that will be located next to it) to see if an exception has been throwed.

Hope this helps,

Thanks for reminding me. I already placed everything in place.

I found the main problem. The dataset should not include “&” because the parser identifies it as a reserved keyword ( ). It throws an exception.

4

erikd:
I found the main problem. The dataset should not include “&” because the parser identifies it as a reserved keyword ( ). It throws an exception.

Actually with next version v1.3.2 all 5 speical XML entities (& < > ’ "e;) will be automatically encoded for you, so this will not generate exceptions anymore.

5

Thanks, Patrick.