| Category: | Feature request |
Priority: | Normal |
Status: | Assigned |
| Project: | Severity: | Minor |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
And I was hoping for the new fancy dancey layout engine to be in it.
10 Comments:
It looks to me like not everyone will want the XHTML exporter to be used by default. Would make sense that this is configurable so that the XHTML output would be treated either as another export option along side Excel etc, or as the default for HTML output?
"It looks to me like not everyone will want the XHTML exporter to be used by default."
Well, you always get your lunatic fringe I suppose.
Frankly the new XHTML renderer looks great when I've tried it in iReport, I can't think of any situation where I wilfully want report elements to be hidden under other ones. An option to use it as the default HTML output would be much appreciated. Having it as a download option seems redundant as there are far nicer download options such as pdf. Also, what would happen to the pagination of a download HTML output?
Was it made configurable then?
It would be great if this was included. Or even an option in some config file to say 'output as XHTML instead of HTML'.
That way, people (like me) with no prior JasperServer knowledge could easily change the default output method without having to delve too deeply into the code.
This chap has worked out a way of doing it.
http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=10...
it requires altering and re-compilation of jasperserver-war-jar-3.7.0.jar and editing DefaultJasperViewer.jsp
I have packaged these changes as a patch at http://jasperforge.org/scm/viewvc.php/JasperServer-3.7.0/Default-XHTML-E...
Need to login to the Forge to see and download this.
One of our user has attempted to deploy the CE patch for the war file and got the following error when executing a JS CE report:
org.springframework.beans.NotWritablePropertyException: Invalid property \'requestParameterAnchor\' of bean class [com.jaspersoft.jasperserver.war.action.ViewReportAction]: Bean property \'requestParameterAnchor\' is not writable or has an invalid setter method.
Can you check the code and see whether the parameter type of the setter match the return type of the getter?
Thanks
Confirmed.
I get the same result when putting static text on image using iReport and JasperServer 3.7.1.
i.e. image disappears.
Sorry to keep harping on the same old string but is it possible to enable XHTML for Jasperreports Server 4?
I've just run into this problem as well so i would love to see it implemented. Ironically when i searched for the problem i found my original post almost a year ago to the day that first asked about it.