Birt Deployment error - is it a bug? [message #542968] |
Sun, 27 June 2010 23:45  |
Eclipse User |
|
|
|
Hi Experts,
I had developed some reports (using connection profile) on my windows machine and had then copied them into the Birt WebViewerExample tomcat application running on windows machine - it worked.
Then I moved the same WebViewerExample app onto a linux machine.
In the connectionProfileStore, I changed the path of jarlist to be correct on the linux environment. (It goes into WebViewerExample\WEB-INF\platform\plugins\.... )
On the linux machine, 'tomcat' user is the owner of this file and (its parent directories) still I am getting this error:
WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
Jun 28, 2010 8:06:36 AM org.eclipse.birt.report.data.adapter.impl.ModelAdapter adaptDataSet
WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
Jun 28, 2010 8:06:37 AM org.eclipse.birt.report.data.oda.jdbc.dbprofile.impl.Connection open(Properties)
WARNING: Unable to open a connection with the database connection profile.
org.eclipse.datatools.connectivity.oda.OdaException: Unable to find the connection profile referenced by the data source connection properties.
at org.eclipse.birt.report.data.oda.jdbc.dbprofile.impl.Connection.open(Connection.java:104)
at org.eclipse.birt.report.data.oda.jdbc.dbprofile.impl.Connection.open(Connection.java:57)
Is it a known bug / limitation of some sort?
Please guide..
Thanks in advance
-Sebastian
[Updated on: Mon, 28 June 2010 09:01] by Moderator
|
|
|
|
|
|
|
|
|
|
Re: Birt Deployment error - is it a bug? [message #642353 is a reply to message #642071] |
Tue, 30 November 2010 18:02  |
Eclipse User |
|
|
|
Umm, it depends on which jarlist property is used.
The jarList property of a driver definition (defined in the workspace as described in my earlier post) does *not* accept relative path, nor any variable.
Since a workspace and thus its driver definition is local to each deployment environment, it is not intended to be portable across systems. So an absolute path specific to a local system should be sufficient.
Whereas, the jarList property defined in a connection profile instance can be portable across deployment systems. It can thus be scripted with variable(s) to specify the root path, as appropriate.
Linda
|
|
|
Powered by
FUDForum. Page generated in 0.30338 seconds