| BIRT Runtime Refuses Manifest [message #486360] |
Thu, 17 September 2009 12:24  |
 Juliane Harbarth
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Hello,
I am using a reporting engine that has been built from the BIRT Runtime
Engine 2.3.2 to display reports using a customized Data Source. This used
to work ok for quite a while, but now we suddenly are having problems,
i.e. the engine throws multiple java exceptions. The reports that it
refuses to execute can be executed by the Eclipse BIRT preview though.
One of the error messages we are getting is the following:
Caused by: java.lang.IllegalArgumentException:
com.centrasite.reporting.datasource.xml
at
org.eclipse.datatools.connectivity.oda.util.manifest.Manifes tExplorer.getExtensionManifest(ManifestExplorer.java:200)
at
org.eclipse.birt.data.engine.odaconsumer.Driver.doGetDriverM anifest(Driver.java:147)
By gradually changing back the engine to what used to work before, I found
that a manifest is the problem. Not the manifest of the driver jar but of
another jar that the driver uses.
This is strange for two reasons. Firstly, the manifest is a result of the
BND tool by Mr. Kriens, and secondly, there are only three not very
significant changes to the manifest from the version which worked. These
changes are
1. Two new classes in the Import-Package clause,
2. plenty of new entries in the Export-Package clause due to 1, and
3. due to 1. and 2. the manifest is now longer.
So, why is the new manifest undigestible for the runtime engine when it is
digestible for the preview runtime, has not much changed, and has been
produced by a knowlegeable tool (BND)?
I would greatly appreciate any advice.
Thanks & regrads,
Juliane.
|
|
|
| Re: BIRT Runtime Refuses Manifest [message #487031 is a reply to message #486360] |
Mon, 21 September 2009 15:21  |
|
Juliane,
Any chance you can post the manifest?
Jason
Juliane Harbarth wrote:
>
> Hello,
>
> I am using a reporting engine that has been built from the BIRT Runtime
> Engine 2.3.2 to display reports using a customized Data Source. This
> used to work ok for quite a while, but now we suddenly are having
> problems, i.e. the engine throws multiple java exceptions. The reports
> that it refuses to execute can be executed by the Eclipse BIRT preview
> though.
> One of the error messages we are getting is the following:
> Caused by: java.lang.IllegalArgumentException:
> com.centrasite.reporting.datasource.xml
> at
> org.eclipse.datatools.connectivity.oda.util.manifest.Manifes tExplorer.getExtensionManifest(ManifestExplorer.java:200)
>
> at
> org.eclipse.birt.data.engine.odaconsumer.Driver.doGetDriverM anifest(Driver.java:147)
>
> By gradually changing back the engine to what used to work before, I
> found that a manifest is the problem. Not the manifest of the driver jar
> but of another jar that the driver uses.
> This is strange for two reasons. Firstly, the manifest is a result of
> the BND tool by Mr. Kriens, and secondly, there are only three not very
> significant changes to the manifest from the version which worked. These
> changes are
> 1. Two new classes in the Import-Package clause, 2. plenty of new
> entries in the Export-Package clause due to 1, and
> 3. due to 1. and 2. the manifest is now longer.
>
> So, why is the new manifest undigestible for the runtime engine when it
> is digestible for the preview runtime, has not much changed, and has
> been produced by a knowlegeable tool (BND)?
>
> I would greatly appreciate any advice.
> Thanks & regrads,
> Juliane.
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03443 seconds
] 
Search
Help
Register
Login
Home
