Home » Archived » BIRT » Really dumb problem with the BIRT tutorial
| Really dumb problem with the BIRT tutorial [message #797877] |
Mon, 13 February 2012 20:10  |
Eclipse User |
|
|
|
I'm working through the BIRT tutorial. I'mat the page "Build a Data Set," and BIRT is not responding as the tutorial says it should.
The instructions worked up to this point:
Find or open the Data Explorer view.
Select the Data Sets node in the tree view.
Right-click to open the context menu.
Select New Data Set. The New Data Set dialog will appear.
Enter "Customers" for the Data Set Name field.
Ensure that the Data Source field shows the Sample data source.
Ensure that the Data Set Type field shows "SQL Select Query".
After that the instructions told me to "Click Next." But the Next button was disabled. BIRT only let me click Finish. When I did that, BIRT opened an error box that contained the message:
Quote:Database 'jar:(c:\Program Files (x86)\eclipse\plugins\org.eclipse.birt.report.data.oda.sampledb_2.0.1\db\Birt: not found.
Reasons: An unexpected internal exception occurred. Please see log for detail.
I clicked the Details button and got this:
Quote:An unexpected internal exception occurred.Please see log for detail.
Plug-in Provider:Eclipse.org
Plug-in Name:BIRT Designer UI
Plug-in ID:org.eclipse.birt.report.designer.ui
Version:2.0.1
Error Code:Error.GUIException.invokedByUnexpectedException
Error Message:Database 'jar:(c:\Program Files (x86)\eclipse\plugins\org.eclipse.birt.report.data.oda.sampledb_2.0.1\db\BirtSample.jar)BirtSample' not found.
Then I clicked OK and got another error box with this message:
Quote:Failed to create a connection. Please verify the connection properties.
When I closed that error box I get a dialog titled "Edit Data Set - Customers" which allowed me to enter a SQL query.
At that point I proceeded to the next step in the tutorial, "Enter the following Query." I entered the specified query and clicked OK. I got an error box that said:
Quote:Cannot open the connection for the driver: org.exclipse.birt.report.data.oda.jdbc
Failed to get conection.
Database 'jar:(C:\Program Files (x86)\...\db\Birt: not found.
Reason: A BIRT exception occurred.
What went wrong? How can I fix it?
|
|
| | | |
| Re: Really dumb problem with the BIRT tutorial [message #804687 is a reply to message #797877] |
Wed, 22 February 2012 17:20  |
| Eclipse User |
|
|
|
Thank you, I tried that but ran into problems.
I downloaded a file from the link you suggested (actually, from a mirror at Oregon State University). The file name is eclipse-reporting-indigo-SR1-win32-x86_64.zip. When I tried to run it I got this message:
Quote:A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run Eclipse. No Java virtual machine was found after searching the following locations: C:\Program Files\eclipse\jre\bin\javaw.exe
javaw.exe in your current PATH
The message is correct that there's no javaw.exe in C:\Program Files\eclipse\jre\bin (actually, there's no C:\Program Files\eclipse\jre directory at all) or in the path. I can get one, but I'm skittish about this because if I applied the requirements in the message to the version of Eclipse that I downloaded first, I'd have to conclude that it won't run either, and it does.
The version you suggested I download is installed in C:\Program Files\eclipse (probably obvious from the message).
The running version that I installed first is a 32-bit version, stored in C:\Program Files (x86)\eclipse.
Neither version has a jre directory.
The only javaw.exe on the computer (presumably a 64-bit version) is in C:\Windows\SysWOW64.
Can you help me make sense of this?
Later --
I tried running the new version of Eclipse from the command line with C:\Windows\SysWOW64 appended to the path.
Windows displayed the "wait" cursor for a few seconds, then returned to a normal cursor, and the command window displayed a new command line prompt.
A long time later (maybe 15 seconds), I got the error box shown in the attachment.
The pathnames with mixed slashes and backslashes drew my attention, and so did the ones with double backslashes. I tried both of those perversions in CD commands, though, and the CLP accepted them.
[Updated on: Thu, 23 February 2012 12:04] by Moderator |
|
| |
| Re: Really dumb problem with the BIRT tutorial [message #805591 is a reply to message #805391] |
Thu, 23 February 2012 18:45 |
| Eclipse User |
|
|
|
That version works, but I'm not out of the woods yet.
I was pleased to find that BIRT was storing report definitions in /users, so when i deleted my original 32 bit version and installed this one, they were preserved.
When I tried to preview the report, however, I got a Java run time error which referred to an undefined class -- the JDBC connector, com.mysql.jdbc.Driver.
The data set definition -- which worked before -- was preserved along with the report definition. I deleted it and tried to recreate it. I found that the Driver Class dropdown no longer listed that driver.
The only JDBC driver in the list was one called "org.apache.derby.jdbc.EmbeddedDriver (Apache Derby Embedded Driver)." I selected that one.
When I tried to preview the report I got another run time error which said, "Failed to find out data source of data set "List classes"."
I looked at the data set "List classes" and found that BIRT had marked it with a red X. I opened it and found that its data source had been changed from the intended one to a different one that was apparently defined by the distribution.
I changed it back and tried to preview again. This time I got a message that said, "There is an error in get connection, No suitable driver found for jdbc:derby:[subsubprotocol:]DATABASE[;ATTRIBUTE=VALUE]*."
So: the only JDBC driver class I was originally using no longer exists, and the only remaining one has no driver.
This adventure is proving to be very painful. I hope you can help me see it through to a successful conclusion.
|
|
|
| Re: Really dumb problem with the BIRT tutorial [message #806300 is a reply to message #805591] |
Fri, 24 February 2012 14:55 |
| Eclipse User |
|
|
|
Jonathan,
When you create a new datasource there is a button to manage drivers.
If you click on it, an editor will be launched that allows you to add
new drivers. It looks like your designer is just missing the mysql driver.
Jason
On 2/23/2012 6:45 PM, Jonathan Sachs wrote:
> That version works, but I'm not out of the woods yet.
>
> I was pleased to find that BIRT was storing report definitions in
> /users, so when i deleted my original 32 bit version and installed this
> one, they were preserved.
>
> When I tried to preview the report, however, I got a Java run time error
> which referred to an undefined class -- the JDBC connector,
> com.mysql.jdbc.Driver.
>
> The data set definition -- which worked before -- was preserved along
> with the report definition. I deleted it and tried to recreate it. I
> found that the Driver Class dropdown no longer listed that driver.
>
> The only JDBC driver in the list was one called
> "org.apache.derby.jdbc.EmbeddedDriver (Apache Derby Embedded Driver)." I
> selected that one.
>
> When I tried to preview the report I got another run time error which
> said, "Failed to find out data source of data set "List classes"."
>
> I looked at the data set "List classes" and found that BIRT had marked
> it with a red X. I opened it and found that its data source had been
> changed from the intended one to a different one that was apparently
> defined by the distribution.
>
> I changed it back and tried to preview again. This time I got a message
> that said, "There is an error in get connection, No suitable driver
> found for jdbc:derby:[subsubprotocol:]DATABASE[;ATTRIBUTE=VALUE]*."
>
> So: the only JDBC driver class I was originally using no longer exists,
> and the only remaining one has no driver.
>
> This adventure is proving to be very painful. I hope you can help me see
> it through to a successful conclusion.
|
|
|
Goto Forum:
Current Time: Sat Jul 19 10:03:57 EDT 2025
Powered by FUDForum. Page generated in 0.06066 seconds |
Home