nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Relative Resource Path for Data Sources

medini_1060067341

Hello,

I currently have my own Medini project template. I've created a folder called "reporting" into the project's config folder where I keep all my .rptdesign and rptlibray files.

My rptdesign has one EMF Data Source which it's Resource Path points out to the .profile file in the root directory of my Medini project. However, BIRT will only let me specify the absolute path to the .profile file.

The problem I am facing right now is that this project will be distributed as a Medini Project Template to other people. Ideally, people should be able to to generate their reports without going into Report Design and changing the path of the data source every time they create a new project from my template. Specifying a relative path to the .profile file of the current project would do it I believe, e.g., something like ../../.profile.

Is it possible to specify a relative path for an EMF data source at all? If not, is there another way I achieve what I want?

Thanks in advance,

Lucas

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Lucas,

sure, I think the attached sample explains it best (maybe you need to change the URL at the data source to get it working). You need to add computed columns to the data set and inside use a JS snippet to extract it.

Happy Reporting

Jan

All comments

medini_1024169437

Hi Lucas,

first I suggest to renamed "reporting" to "reports", so "<project root>/config/reports", that fodler is scanned and available reports are shown in the Reports context menu.

Second I am not sure why you want to load the .profile file. This is a very special resource.

Thirs I am not sure why relative resources should not work, in whic context you use them?

Happy Reporting

Jan

medini_1060067341

Hi Jan,

2) Which file would you suggest I use instead? .project.medini? I have been loading the .profile file because it just works

3) So this is what happens when I try to load the resource using a relative path:

It seems like Medini is looking for the file within its installation folder instead of looking for it within the current project's folder like I would like it to.

Thanks,

Lucas

medini_1024169437

Ah, that rings a bell, so you are trying to load the medini EMF models "yourself" using an EMF data source.

I think that wont work perfectly. Medini has its own way or loading multiple resources in a resource set + having customizations to support project based custom profiles.

I attached a self learning slide deck, maybe that explains the different approached you have.

Jan

Update: I updated the attachment with a newer version

medini_1060067341

Hi Jan,

Could you also share a best practices project for reporting with me (preferably including both scripted and OCL data sources)?

I am still struggling to understand how the scripted Data Sources are supposed to work in practice and how to make OCL Data Sources "project generic".

Thanks,

Lucas

medini_1024169437

Hi Lucas,

find attached a ZIP file with simple samples that were created to underpin the training.

Hope that helps.

Jan

medini_1060067341

Hi Jan,

Thanks for the examples. They helped me a lot!

I am still facing a few issues with scripted data sources though and retrieving entities of certain meta-classes. For example, I am not able to retrieve StaticChecklistItems using a scripted data source (by creating a data set called StaticChecklistItemDS).

For other meta-classes such as Vulnerabilities, the scripted data sources work just fine (by creating a data set called VulnerabilityDS).

How can I retrieve checklist items using a scripted datasource?

Thanks,

Lucas

medini_1024169437

Lucas,

checklist items are a bit special, there is the base class ChecklistItem and two different sub-stypes for statc and dynamic checklist items. For some reason you cannot address the statuc one directly Instead, use the base class and then SCDS suffix instead of DS, so use

ChecklistItemSCDS

as the name for the data source and it should work.

Happy Reporting

Jan

medini_1060067341

Hi Jan,

ChecklistItemSCDS works fine for default Medini ChecklistItems attributes such as "note".

However, for custom attributes, e.g., user_my_attribute, it doesn't. Is there a way to print the contents of custom checklist columns/attributes into reports?

Thanks,

Lucas

medini_1024169437

Well, it works for SafetyGoalDS, right?

My gut feeling is that this is a limitationm due to the SCDS suffix: it handles sub-class instances but not the metamodel of subclasses :-/

I'm afraud you have to switch to OCL based DS.

Jan

medini_1060067341

Hi Jan,

If I need to use an OCL-based DS for checklists, then I am back to my original issue again :-/

How can I have an OCL DS and still guarantee that the reports will be generated without me having to go into the Report Design perspective and manually changing the OCL DS resource path for every new project?

Lucas

medini_1024169437

I am not sure about that question, OCL is just another way of developing your data set, that's exchangeable with the other two ways of doing it.

There was an example of how the OCL DS would look like in the ZIP, maybe you have a look.

Maybe what confuses you is that the OCL data source can be bound to a project at *design* time but that only for the design time,

at runtime it is automatically bound to the project which is used to generate the report.

Happy Reporting

Jan

medini_1060067341

The issue I am facing however, is that the tool always throws an error when I try to generate a report after doing the following:

1) I create the .rptdesign file containing an OCL DS within a project. The OCL DS points to the .project.medini file in the root directory of the project which my .rptdesign belongs to (just like in the example you shared).

2) I export the project as a .mprx

3) Then I create a new workspace and assign the exported project's .mprx file as a template in the preferences menu (Window->Preferences->General->Project Templates)

4) Then I create a new project using the template I just specified

When I run the report generation I get the following error:

An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: VulnerabilityOCL
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Base Project Template v5/.profiling' does not exist.
An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: VulnerabilityOCL
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Base Project Template v5/.profiling' does not exist.
Failed to prepare the query execution for the data set: VulnerabilityOCL
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Base Project Template v5/.profiling' does not exist.
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Base Project Template v5/.profiling' does not exist.
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Base Project Template v5/.profiling' does not exist.
org.eclipse.core.internal.resources.ResourceException: Resource '/Base Project Template v5/.profiling' does not exist.
Resource '/Base Project Template v5/.profiling' does not exist.
Resource '/Base Project Template v5/.profiling' does not exist.
Invalid javascript expression: ReferenceError: "row" is not defined. (<inline>#1)
Invalid javascript expression: ReferenceError: "row" is not defined. (<inline>#1)
ReferenceError: "row" is not defined. (<inline>#1)

The report generation works just fine when done in the original project from step 1). Am I missing something?

It seems to me that the report runtime is looking for the .profile file within the original project's folder and is not able to find it.

Thanks,

Lucas

medini_1024169437

My understanding is that not the data source (referencing the .project.medini file) is the problem but you still have somehow a reference to the .profile fole in your scripts or somewhere else. I dont think its related to the OCL data set or source. Could you double check whether there is anything left from your previous attempt to solve this issue?

Jan

medini_1060067341

Hi Jan,

I don't think that's the case because if I delete my OCL DS entirely from the project and generate my report based on the scripted DS only, it works just fine. So my assumption is that it can't be due to a leftover reference to the .profiling file within my project.

I've ran a few more tests and I only get the error above when I create a new project from a template. If I export my project from the original workspace and then import it into a different workspace, reporting works just fine.

Any ideas on how do I get it to work with projects created from a template?

medini_1024169437

Hm, thats very strange. One idea: open the rptdesign as text (or open the appropriate ta in the design editor) and search for .profiling.

Does it occur only once at the data source or somewhere else as well?

What if you bind the data source to some other project (that should not affect the report generation) but does it impose another error?

Jan

medini_1060067341

Hi Jan,

1) I just opened the rptdesign as text and looked for .profiling and couldn't find anything.

2) The error only occurs when I have an OCL DS. If I only have scripted DSs in my rptdesign, then the generation works just fine.

3) I went ahead and created a fresh project named "Test" and a fresh rptdesign within it with one OCL DS and tried to print StaticChecklistItem names.

Then I exported the project as an .mprx file ("Test_Project.mprx"), created a completely new workspace, configured the .mprx as a template and created a new project from the template called "Project1".

I still get the same error when trying to generate the report. What's interesting to me, is that the BIRT runtime is looking for the .profiling file within "Test" which is the project I exported as an .mprx initially and which "Project1" is based upon:

An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: ChecklistItemOCL
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Test/.profiling' does not exist.
An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: ChecklistItemOCL
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Test/.profiling' does not exist.
Failed to prepare the query execution for the data set: ChecklistItemOCL
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Test/.profiling' does not exist.
Failed to prepare the following query for the data set type (org.eclipse.emf.oda.ecore.dataSet).
[self]
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Test/.profiling' does not exist.
org.eclipse.datatools.connectivity.oda.OdaException ;
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.core.internal.resources.ResourceException: Resource '/Test/.profiling' does not exist.
org.eclipse.core.internal.resources.ResourceException: Resource '/Test/.profiling' does not exist.
Resource '/Test/.profiling' does not exist.
Resource '/Test/.profiling' does not exist.

So I went ahead and created another project from the template and called it "Test". Everything works fine if I try to generate my report from it.

Is there a way to force the BIRT runtime to look for the .profiling file within the the project from which I invoke it from?

Thanks,

Lucas

medini_1024169437

Lucas,

are you able to post these tets projects here? I have no cluse about whats going on.

I need to run it and check. It looks like there is already some problem in the project and not the report design.

Could you as an alternatuve run the Diagnose? (Project -> Right Click -> Check Consistency

Happy Reporting

Jan

medini_1060067341

Hi Jan,

Please find the .mprx attached.

Thanks,

Lucas

medini_1024169437

Lucas,

I can reproduce and this looks very very strange.

Stay tuned, I have no solution yet. seems to be a ... defect.

Jan

medini_1024169437

Lucas, we finally found the root cause for this. Took us some time, sorry,

You have selected a "dynamic profile class" as the OCL context class, visible by the P suffix of the package:

This leads to a fixed reference to the Test project's profile, hence wont work in other projects, and even worse, causes some strange problems afterwards.

Please do NOT use any of these profile classes in any OCL data set but always use the main metamodel classes from the medini metamodel. Using profile dynamic classes is not supported at the moment.

Regards

Jan

medini_1060067341

Hi Jan,

Thanks for taking the time to look into this.

The issue of not using dynamic profile classes as the OCL context and/or result classes is that I cannot retrieve my custom meta-class attributes, e.g., user_custom_attribute in the model attached.

Is there any way to use the non-dynamic profile classes and still retrieve my custom attributes somehow?

Thanks,

Lucas

medini_1024169437

Hi Lucas,

Happy Reporting

Jan

medini_1024169437

Just to add that we fixed this behavior in 22.2 - namely you cant select an "dynamic profile" class (with P suffix) anymore.

Jan