Bug 131325 - JSR-170 Java Content Repository
Summary: JSR-170 Java Content Repository
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Wenbin He CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 09:38 EST by Rick Milheron CLA
Modified: 2007-07-27 16:10 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Milheron CLA 2006-03-10 09:38:01 EST
We request that BIRT be enhanced to support a JSR-170 compliant Java Content Repository as a data source.  See the following exchange, and feel free to contact me with any questions, comments, etc.


Rick,

One of the great things about open source is the opportunity to get a look at all the interesting new projects that are out there.  JCR and Jackrabbit are new ones for me, but they look very promising.

BIRT has left the entire storage side of reports both for the report designs and report documents open, so there is no built in support for JCR or JSR-170.

If you could provide an enhancement request for JCR support we can look at adding it in a future BIRT release.  We track enhancements in Bugzilla https://bugs.eclipse.org/bugs/enter_bug.cgi?product=BIRT.

Scott Rosenbaum
BIRT PMC
Comment 1 jluo CLA 2006-03-13 00:08:42 EST
Looks like the bug reporter needs a new ODA data source which can support JSR-170 compliant Java Content Repository. If so, we need a lot of time to implement it for driver and UI, and then I put it into 2.1.0 final as temp target.
Comment 2 jluo CLA 2006-03-13 21:50:23 EST
Wenfeng, can you set its target?
Comment 3 Wenfeng Li CLA 2006-03-14 22:06:25 EST
This is an enhancement in the web viewer/engine/design engine area.  Need to define a URI for files/resources in a JSR 170 repository so that report engine can open report designsm report doc in it, load resources in it, and/or generate report doc in it.
Comment 4 Ken Geis CLA 2007-07-27 16:10:20 EDT
Wenfeng's interpretation in comment #3 is a separate feature.  I think that the description and comment #1 are more accurate.  I think he wants to run a query against a JSR-170 repository and then be able to use the metadata and content in a report.