| ODA for search engine [message #18473] |
Mon, 14 March 2005 10:45  |
Eclipse User |
|
|
|
Originally posted by: torgeir.fast.no
Hi,
I've fooled around with BIRT a bit and must say I'm very impressed so far!
So I started out to write a ODA plugin for our search engine to see if that
is possible. This is how far I've gotten:
- DataSource and DataSet wizards to configure the search engine connections
- ODA implementation for our search engine up to the point where I get:
a) All column-names available in the Data Explorer
b) Preview results in the "Edit Data Set" dialog
When I construct a report however I get an error message when trying to
preview the report:
Error Message
Semantic errors in
C:\eclipse\runtime-workspace\test\reports\baz.rptdesign.
The value of the property "keyExpr" is required.
Any help is greatly appreciated!
Torgeir,
Architect
Fast Search & Transfer, Inc. http://www.fastsearch.com/
|
|
|
|
| Re: ODA for search engine [message #20631 is a reply to message #20587] |
Sat, 19 March 2005 00:45  |
| Eclipse User |
|
|
|
Torgeir,
The development team is reworking the ODA interfaces. They'll be creating
Javadoc that should be the only documentation you need to create a custom
driver.
At present, the BIRT engine runs within your Eclipse process. To debug a
driver within BIRT, you'll have to launch a separate Eclipse instance for
the BIRT designer the same as if you were debugging an Eclipse plugin. Then,
preview your report (using the Preview tab) and execution should stop at
breakpoints within your driver. I've not tried this, but based on
discussions with the developers, it seems that this should work.
Once the updated ODA is available, perhaps someone in the community can
create a simple ODA unit test framework. It should be relatively easy to
test an ODA driver by itself without the complexity of debugging your driver
within the context of the overall BIRT engine.
- Paul
Paul Rogers
BIRT PMC
"Torgeir Hovden" <torgeir@fast.no> wrote in message
news:d1er5t$t2j$1@www.eclipse.org...
> I've gotten a step further, it's unclear how, but I still don't get any
> data the previewed reports. As far as I can see no query is ever executed
> although the table is bound to the correct Data Set. For a JDBC Data Set
> things work fine.
>
> Any ideas? How can I best debug this? Is there any sequence diagrams or
> simular available that shows the highlevel execution of report generation
> in relation to the data sets / sources?
>
> Thanks,
> Torgeir
>
> "Torgeir Hovden" <torgeir@fast.no> wrote in message
> news:d14bjc$1kq$1@www.eclipse.org...
>> Hi,
>>
>> I've fooled around with BIRT a bit and must say I'm very impressed so
>> far! So I started out to write a ODA plugin for our search engine to see
>> if that is possible. This is how far I've gotten:
>>
>> - DataSource and DataSet wizards to configure the search engine
>> connections
>> - ODA implementation for our search engine up to the point where I get:
>> a) All column-names available in the Data Explorer
>> b) Preview results in the "Edit Data Set" dialog
>>
>> When I construct a report however I get an error message when trying to
>> preview the report:
>>
>> Error Message
>> Semantic errors in
>> C:\eclipse\runtime-workspace\test\reports\baz.rptdesign.
>> The value of the property "keyExpr" is required.
>>
>>
>> Any help is greatly appreciated!
>>
>> Torgeir,
>> Architect
>> Fast Search & Transfer, Inc. http://www.fastsearch.com/
>>
>
>
|
|
|
| Re: ODA for search engine [message #25145 is a reply to message #20631] |
Wed, 06 April 2005 09:08 |
| Eclipse User |
|
|
|
Originally posted by: torgeir.fast.no
Paul,
A driver test framework sounds great. I already debug within Eclipse, but
find it difficult since it seems like my driver is not called at all during
report preview (but works fine up to that point including data-set preview).
I've updated to the latest stable build and have the same issues.
Torgeir
"Paul Rogers" <progers@actuate.com> wrote in message
news:d1geak$645$1@www.eclipse.org...
> Torgeir,
>
> The development team is reworking the ODA interfaces. They'll be creating
> Javadoc that should be the only documentation you need to create a custom
> driver.
>
> At present, the BIRT engine runs within your Eclipse process. To debug a
> driver within BIRT, you'll have to launch a separate Eclipse instance for
> the BIRT designer the same as if you were debugging an Eclipse plugin.
> Then, preview your report (using the Preview tab) and execution should
> stop at breakpoints within your driver. I've not tried this, but based on
> discussions with the developers, it seems that this should work.
>
> Once the updated ODA is available, perhaps someone in the community can
> create a simple ODA unit test framework. It should be relatively easy to
> test an ODA driver by itself without the complexity of debugging your
> driver within the context of the overall BIRT engine.
>
> - Paul
>
> Paul Rogers
> BIRT PMC
>
> "Torgeir Hovden" <torgeir@fast.no> wrote in message
> news:d1er5t$t2j$1@www.eclipse.org...
>> I've gotten a step further, it's unclear how, but I still don't get any
>> data the previewed reports. As far as I can see no query is ever executed
>> although the table is bound to the correct Data Set. For a JDBC Data Set
>> things work fine.
>>
>> Any ideas? How can I best debug this? Is there any sequence diagrams or
>> simular available that shows the highlevel execution of report generation
>> in relation to the data sets / sources?
>>
>> Thanks,
>> Torgeir
>>
>> "Torgeir Hovden" <torgeir@fast.no> wrote in message
>> news:d14bjc$1kq$1@www.eclipse.org...
>>> Hi,
>>>
>>> I've fooled around with BIRT a bit and must say I'm very impressed so
>>> far! So I started out to write a ODA plugin for our search engine to see
>>> if that is possible. This is how far I've gotten:
>>>
>>> - DataSource and DataSet wizards to configure the search engine
>>> connections
>>> - ODA implementation for our search engine up to the point where I get:
>>> a) All column-names available in the Data Explorer
>>> b) Preview results in the "Edit Data Set" dialog
>>>
>>> When I construct a report however I get an error message when trying to
>>> preview the report:
>>>
>>> Error Message
>>> Semantic errors in
>>> C:\eclipse\runtime-workspace\test\reports\baz.rptdesign.
>>> The value of the property "keyExpr" is required.
>>>
>>>
>>> Any help is greatly appreciated!
>>>
>>> Torgeir,
>>> Architect
>>> Fast Search & Transfer, Inc. http://www.fastsearch.com/
>>>
>>
>>
>
>
|
|
|
|
|
| Re: ODA for search engine [message #25954 is a reply to message #25306] |
Tue, 12 April 2005 02:11 |
| Eclipse User |
|
|
|
Torgeir,
The solution today is to make multiple copies of the JDBC driver (or
configure ODA to find your driver in a single location, but you still must
make the ODA entry thee times.) The team is aware of this issue and is
looking into ways to resolve it before Release 1 next month.
- Paul
Paul Rogers
BIRT PMC
"Torgeir Hovden" <torgeir@fast.no> wrote in message
news:d336al$t2m$1@news.eclipse.org...
> Aleksander,
>
> Thanks - that lead me on the right path. It seems that
> org.eclipse.birt.report.viewer requires the drivers under it's directory
> hierarchy - e.g.
> C:\eclipse\plugins\org.eclipse.birt.report.viewer_0.0.1\birt -viewer\WEB-INF\plugins\drivers\.
> Dropping it in there solved the problem!
>
> This seems somewhat inconsistent with the designer, which works with the
> plug-in directly. BIRT gurus: where should the driver reside? I don't like
> duplicating the jars all over...
>
> Torgeir
>
> "Aleksander Bandelj" <aleksander.bandelj@academa.si> wrote in message
> news:d31k8t$v7$1@news.eclipse.org...
>> This has bitten me as well and seems to be plugin classloader issue.
>> Preview works after adding database driver jar to boot class path.
>>
>> Torgeir Hovden wrote:
>>
>>>Paul,
>>>
>>>A driver test framework sounds great. I already debug within Eclipse, but
>>>find it difficult since it seems like my driver is not called at all
>>>during report preview (but works fine up to that point including data-set
>>>preview).
>>>
>>>I've updated to the latest stable build and have the same issues.
>>>
>>>Torgeir
>>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03552 seconds
Home