[
http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teodoro Cue Jr. updated MRM-329:
--------------------------------
Attachment: MRM-329-archiva-webapp-20070725.patch
MRM-329-archiva-database-20070725.patch
I've attached a preliminary work of how archiva can use JasperReports as its
reporting mechanism. It's functional but there are a lot of aesthetics work to
be done.
Aside from the look, there are a lot of things to discuss:
1. Do we need to put in the links for the pages? Such as, when using Google,
there are a number of links that corresponds to the resulting pages. Example:
<1><2><3>...<Last Page>
2. Do we put in the functionality that a user can choose the resulting number
of rows per page? Currently I've hard coded this to 10 rows per page as I don't
have a lot of sample to work on. And it's hard to put this number in between
pages. It would be better to have the user choose the number first before
starting the report. We can't put an editable text field on the JasperReport
page. Or I just can't find a sample of it on the web. ^_^
3. The last page for now is blank. Will work on this maybe tomorrow. Depends on
the responds I get from the list or here.
4. I've queried the DB straight from the action. I understand the DB management
quite well but had a hard time understanding the ReportingManager. Would it be
better to wrap the DB queries from ReportingManager?
5. This is related to item 4. As I don't understand the ReportingManager fully
and I need to get a limited number of rows. I've added a range constraint that
would do this. I'm not sure on this implementation. JPOX documentation says
that it's only "implemented efficiently" on a couple of DBs.
http://www.jpox.org/docs/1_2/jdo/query.html
6. Anyone who can point me to a good jrxml document would be helpful. I can't
seem to have <staticText> working. So I use <textField> instead.
Feedback will be greatly appreciated. :)
Thanks!
> The Reports link gives an HTTP 500
> ----------------------------------
>
> Key: MRM-329
> URL: http://jira.codehaus.org/browse/MRM-329
> Project: Archiva
> Issue Type: Bug
> Components: reporting
> Affects Versions: 1.0-alpha-1
> Reporter: Napoleon Esmundo C. Ramirez
> Assignee: Joakim Erdfelt
> Priority: Blocker
> Fix For: 1.0.x
>
> Attachments: MRM-329-archiva-database-20070725.patch,
> MRM-329-archiva-webapp-20070725.patch
>
>
> Clicking the Reports link in the side navigation menu displays the following
> (edited/snipped stacktrace):
> HTTP ERROR: 500
> RequestURI=/admin/reports.action
> Caused by: javax.el.PropertyNotFoundException: The class
> 'org.apache.maven.archiva.reporting.artifact.OldArtifactReport' does not have
> the property 'groupId'.
> at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:574)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:280)
> at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
> at com.sun.el.parser.AstValue.getValue(AstValue.java:118)
> at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
> at
> org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:974)
> at
> org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspx_meth_c_forEach_0(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:143)
> at
> org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp._jspService(org.apache.jsp.WEB_002dINF.jsp.reports.reports_jsp:85)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
