Eclipse Community Forums: BIRT » DataSource and DataSet Properties

Home » Archived » BIRT » DataSource and DataSet Properties

DataSource and DataSet Properties [message #161375]

Tue, 16 May 2006 07:11

Eclipse User

When I define properties for a ODADataSource and ODADataSet, these
are shown on the PropertyBinding-Tab.
Can anybody tell me what must be done to transfer the changes from
the propertyBinding-Tab to the Connection-properties in the code?
Currently, editing the values has no effect...

I use BIRT 2.1RC2 (but 2.0.1 shows the same effect...)

Thanks
Peter

Re: DataSource and DataSet Properties [message #161631 is a reply to message #161375]

Tue, 16 May 2006 20:22

Eclipse User

Peter,

I am not 100% certain that I understand the question.
Do you have the properties writting back and forth with your design file?
Ie do your changes to property binding get saved? If so the Property
Binding should be automatic for all public properties. It is important to
note that the property binding will not be used when doing a preview within
the Data Set editor, but will happen when you preview the report.

Jason

"Peter Fopma" <peter.fopma@ifb-group.com> wrote in message
news:4422c70b189c326be28c1dc03970d723$1@www.eclipse.org...
> When I define properties for a ODADataSource and ODADataSet, these
> are shown on the PropertyBinding-Tab.
> Can anybody tell me what must be done to transfer the changes from
> the propertyBinding-Tab to the Connection-properties in the code?
> Currently, editing the values has no effect...
>
> I use BIRT 2.1RC2 (but 2.0.1 shows the same effect...)
>
> Thanks
> Peter
>
>

Re: DataSource and DataSet Properties [message #162501 is a reply to message #161631]

Thu, 18 May 2006 11:52

Eclipse User

Jason, thanks for your answer.
I could verify that the data is passed to the ODA datasource when the
report is previewed.
Unfortunately my metadata is dependent on the query. Thats why I cannot
design a report unless the query is passed to the ODA datasource and
consequently never noticed that the data is transferred...

Is this a misunderstanding on my behalf or how can I design a report
when the metadata is only available at runtime? (It's the same issue
when using SQL - the SQL-Query defines the metadata...)

Could you explain how this is to be used?

Thanks
Peter

Re: DataSource and DataSet Properties [message #162665 is a reply to message #162501]

Thu, 18 May 2006 17:54

Eclipse User

Peter,

I think we may be crossing wires here :>
I was referring only to the property binding entry.
For example if you use the standard JDBC driver and build a query, this is
automatically passed at design time
to retrieve the meta data. If you put in a value for queryText in the data
binding tab this is only passed at runtime.
We still may not be talking about the same thing.

Jason

"Peter Fopma" <peter.fopma@ifb-group.com> wrote in message
news:c64c58f470a07fb86552d59d68dfd14b$1@www.eclipse.org...
> Jason, thanks for your answer.
> I could verify that the data is passed to the ODA datasource when the
> report is previewed.
> Unfortunately my metadata is dependent on the query. Thats why I cannot
> design a report unless the query is passed to the ODA datasource and
> consequently never noticed that the data is transferred...
>
> Is this a misunderstanding on my behalf or how can I design a report
> when the metadata is only available at runtime? (It's the same issue
> when using SQL - the SQL-Query defines the metadata...)
>
> Could you explain how this is to be used?
>
> Thanks
> Peter
>
>

Re: DataSource and DataSet Properties [message #162800 is a reply to message #162665]

Fri, 19 May 2006 04:56

Eclipse User

OK. I will try to put this straight.

I implemented my own ODA-datasource. The datasource and the dataset
both have properties of their own, which I declared in the plugin.xml.

<plugin>
<extension
point="org.eclipse.datatools.connectivity.oda.dataSource">
<dataSource
...
</dataSource>
<dataSet
defaultDisplayName="%dataset.listname"
id="org.eclipse.birt.report.data.oda.mydataSet">
<properties>
<propertyGroup
defaultDisplayName="Properties for dataset"
name="PropertiesForDataset">
<property
type="string"
defaultDisplayName="Some Property"
canInherit="true"
name="SOMEPROPERTY"/>
</propertyGroup>
</properties>
...
</dataSet>

On the property binding tab I can now find an entry field for 'Some
Propery'.
Values I enter here are saved in the design file.

I now look for a way to use this property at designtime to create a query
and evaluate the metadata.

When I enter something for the query text property for the dataset this
value is used as query when I preview the report. The same is true for
properties I defined for the datasource. The flatfile datasource and the
jdbc datasource create wizardpages to evaluate the properties at design
time. As soon as I enter some garbage for the query text in the property
binding tab the preview fails because this entry replaces the query...

Is there a way to use the entries from the property binding page at design
time without having to implement a complete wizard?

Thanks for your help

Peter

Re: DataSource and DataSet Properties [message #163014 is a reply to message #162800]

Fri, 19 May 2006 12:46

Eclipse User

Peter,

I looked at this for awhile, and I dont see an easy way of doing it.
Property Binding is stored in the model and from there to the design file.
Unless you have access to the model from your page I dont see a way of doing
this.
My first thought was to just read it from the xml design, but it may not be
in there yet.
Property binding is a BIRT operation above ODA and is really not intended to
be the main GUI for the
data set/source properties. I wish I would have had better success.

Jason

"Peter Fopma" <peter.fopma@ifb-group.com> wrote in message
news:3d918d66a7d9a8f055972ea06a98efb1$1@www.eclipse.org...
> OK. I will try to put this straight.
>
> I implemented my own ODA-datasource. The datasource and the dataset
> both have properties of their own, which I declared in the plugin.xml.
>
> <plugin>
> <extension
> point="org.eclipse.datatools.connectivity.oda.dataSource">
> <dataSource
> ...
> </dataSource>
> <dataSet
> defaultDisplayName="%dataset.listname"
> id="org.eclipse.birt.report.data.oda.mydataSet">
> <properties>
> <propertyGroup
> defaultDisplayName="Properties for dataset"
> name="PropertiesForDataset">
> <property
> type="string"
> defaultDisplayName="Some Property"
> canInherit="true"
> name="SOMEPROPERTY"/>
> </propertyGroup>
> </properties>
> ...
> </dataSet>
>
> On the property binding tab I can now find an entry field for 'Some
> Propery'.
> Values I enter here are saved in the design file.
>
> I now look for a way to use this property at designtime to create a query
> and evaluate the metadata.
>
> When I enter something for the query text property for the dataset this
> value is used as query when I preview the report. The same is true for
> properties I defined for the datasource. The flatfile datasource and the
> jdbc datasource create wizardpages to evaluate the properties at design
> time. As soon as I enter some garbage for the query text in the property
> binding tab the preview fails because this entry replaces the query...
>
> Is there a way to use the entries from the property binding page at design
> time without having to implement a complete wizard?
>
> Thanks for your help
>
> Peter
>
>

Previous Topic:	Pseudo-elements and -classes in css?
Next Topic:	Progressive paginated HTML/PDF viewing question on rptdocument

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Oct 03 17:02:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter