narcism

This usually happens when you compile java 1.6 code with 1.5 compliance. How are you compiling the jr trunk?

I discovered most of these issues while testing on IE8 with IE7 compatibility mode on. To address these, for both the html and xhtml exporters we've adjusted the line-height from '1' to 'normal'; and now the 'line-height' attribute is set on the span that contains the text with font-size, for proper calculation. Also, 'Proportional' line spacing for the html exporter now behaves like the one in the xhtml exporter: it uses a float number instead of percentage. You need to check out the jasperreports repository for these changes.

The report used to hang when filling and this has been fixed in jasperreports 4.1.3. As for the splitting issue, please see my comment in the related issue that I've just added.

Could we see the jrxml that you used? We also need the html that is placed inside the htmlcomponent, or an equivalent one. Also, what is the value for the net.sf.jasperreports.html.printelement.factory property in your jasperreports.properties file from the htmlcomponent's jar?

The rotation feature is present only in the xhtml exporter. Have you tried it?

Since the HTML component produces an image, it behaves like an image in general. It will stretch according to content when setting scale type to 'real height' or 'real size', but will entirely overflow when the available height is less than the image's height. You should check out the repository for the latest updates on the html component sample.

1. Don't use JRXmlUtils.parse(...). As I explained here ( http://jasperforge.org/plugins/mantis/view.php?id=4500), it uses a DocumentBuilderFactory that is not namespace aware by default. Instead you shoud use something like this: DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance(); dbf.setValidating(false); dbf.setIgnoringComments(true); dbf.setNamespaceAware(true); DocumentBuilder builder = dbf.newDocumentBuilder(); Document document = builder.parse(JRLoader.getLocationInputStream("data/documentRDF.xml")); params.put(JRXPathQueryExecuterFactory.PARAMETER_XML_DATA_DOCUMENT, document); ... The bolded line is what matters in this case. 2. Pay attention when you set the query executer factories. In your properties file you have: net.sf.jasperreports.query.executer.factory.XPath = ... and in your report you use: <queryString language="xPath">... Notice the case of the 'X' in both situations? It must be the same, otherwise the factory is the default one configured with the lower case 'X' in default.jasperreports.properties: net.sf.jasperreports.query.executer.factory.xPath = ...

Hi, Check the last response on this tracker: http://jasperforge.org/plugins/mantis/view.php?id=4500 There I explain what needs to be done for solving the namespace problem Regards, Narcis

You can check out the SVN for the new sample, jsondatasource, in jasperreports.

We have tried to compile a Jasper report in Google App Engine and it crashes with a: 'java.lang.NoClassDefFoundError: java.awt.Color is a restricted class. Please see the Google App Engine developer's guide for more details' message. So it is unlikely that JasperReports will soon support the Google App Engine since it is tightly coupled with java.awt package. As for using the Apache Harmony implementation for the restricted classes it is also unlikely for now, as we are having difficulties in running our reports in Harmony's DRLVM.

We have added the "rotation" property on the Barbecue barcode component. Its values are the same as for the "rotation" property in the "style" element: None, Left, Right and UpsideDown; it can be set directly on the component or it can be inherited from the style associated with the report element.