Servoy Forum

Hello,

We have just released the 3rd beta for version 3.1.0 of the plugin; it is available as a single jar file download at http://code.google.com/p/servoy-jasperr ... loads/list, which should replace the beta 2 jar file in the /application_server/plugins directory of your Servoy installation directory.

This beta contains fixes for the font extension usage issue, addressed both in Smart Client and in Web Client.

In what follows, we are giving details regarding the usage of font extension jars and the plugin.

The users of the Basic and ChartNScript versions of the plugin should do to the following:
- first a font extension jar can be exported using iReport, via the Tools->Options->Fonts.
- secondly the exported font extension jar should be copied in the /plugins/servoy_jasperreports folder.
- thirdly, from your JasperReports Project lib folder (you need v.3.7.1 for the current version of our plugin) copy the spring-beans and spring-core jars into the /plugins/servoy_jasperreports folder; if you do not have the JasperReports project, along with its libs, please refer to http://jasperforge.org/projects/jasperreports and download version 3.7.1.
- fourthly, you need to modify your servoy_jasperreports.jar.jnlp file accordingly to the changes done above; simply add the following lines to the jnlp file:
<jar href="/plugins/servoy_jasperreports/spring-beans-2.5.5.jar" download="lazy"/>
<jar href="/plugins/servoy_jasperreports/spring-core-2.5.5.jar" download="lazy"/>
<jar href="/plugins/servoy_jasperreports/font_extension.jar" download="lazy"/>

The users of the Advanced version of the plugin should pay attention to the following:
- when configuring the plugin, simply uncomment the spring-core and spring-beans entries from the servoy_jasperreports.properties file and then build the plugin
- then, copy the font extension jar file to the /plugins/servoy_jasperreports folder and add a corresponding entry for this in the servoy_jasperreports.jar.jnlp file, as described above.

We await your feedback!

Regards,
Andrei

Hi Andrei ,

- secondly the exported font extension jar should be copied in the /plugins/servoy_jasperreports folder.

Not too pleased with this solution. Font jars are up to the customer so we want to keep them apart from the Servoy\plugins map. (plugins map can be overwritten with solution update in our opinion)

I would think the Jasper Extra Directory (setting in Application Server) would be the perfect place for those font jars !

Reaction please...

@lwjwillemsen: +1

@Andrei: does that mean, that the jasper-viewer now also can use the fonts inside this font extension jar?
or is the jasper-viewer still depended if the fonts that are really installed locally?

Hi Harjo ,

Very good question ! My colleague just asked the same...

A Servoy reaction on this please...

When will this plugin move to servoyforge?

Was issue 26 addressed? It appears not.

@Harjo: yes, the jasper-viewer can also use the fonts in the font extension jar.

lwjwillemsen wrote:I would think the Jasper Extra Directory (setting in Application Server) would be the perfect place for those font jars !

We are investigating that option too.

Rob

jbader wrote:Was issue 26 addressed? It appears not.

Not yet

Rob

Hi all!

Regarding this release, we are in troubles with signing code... You can see a post in Google Group here

By now, we are deploying our signed .jar (spring-beans-2.5.5.jar, spring-core-2.5.5.jar and .jar of fonts) through beans folder and it seems to be working right...

Updated in Google Group!

What happens, while the server is running, we upload a new report, and there are some new fonts in it. we create a new font extension.jar en upload that to the server.
Do we have to restart the server?

I think for the new extention jar the server has to be restarted but I am not sure. How do you deploy the jar? In the plugin or with the extra directory?

Regards

Stefan

I'm still using the older version of, and the only one that is NOT beta, because I had so many issues regarding fonts, with the first 3.0 beta's

In this older version, we use the extrafonts folder, to add fonts on the fly, the positive thing about this new version, is that you now can use your own fonts in the jasper-viewer (which could not be done, when you store fonts in that extra font folder, on the server)

But if we have to restart every time the server, because we have a new fonts.jar, that would be a not so nice.
Did'nt test it yet, just asking, if this is the case.....