Home » Archived » BIRT » ODA Drivers Configuration - Retiring odaconfig.xml
| ODA Drivers Configuration - Retiring odaconfig.xml [message #25667] |
Mon, 11 April 2005 14:27  |
Eclipse User |
|
|
|
In response to the feedback we received from the community, we are
moving an ODA driver's configuration info from its own file
(odaconfig.xml) to its Eclipse plugin manifest.
The two ODA drivers included in BIRT (jdbc and flatfile) have migrated
to this new ODA plugin implementation. See their plugin.xml for
examples on how the configuration info are now specified.
The ODA runtime driver extension point schema can be found in CVS BIRT
source tree: org.eclipse.birt.data.oda/schema/odaDriverRuntime.exsd.
Use the Eclipse PDE Tools to see its reference document. Most elements
that used to be in the odaconfig.xsd are now defined directly in the
extension point schema.
As part of this change, the ODA run-time framework no longer directly
provides a separate URLClassLoader to load each ODA driver's library
files (specified in <DriverLibraries> in the odaconfig.xml ). Instead,
an ODA driver's class loading in the Eclipse environment is now
delegated to the Eclipse class loading framework via OSGi. Therefore,
the list of run-time library files are now specified in the <runtime>
element in the ODA runtime extension's plugin.xml.
In the BIRT Viewer application environment, the server class loading
framework currently uses a single class loader to load all plug ins.
What this means is that it cannot handle multiple ODA plugging that use
conflicting versions of the same package. The class loading framework
is being enhanced to fully adopt the Eclipse class loading behavior,
e.g. use separate class loader for each plugin.
Note that the above applies to the generic ODA run-time framework. We
are looking into additional solution to address other ODA configuration
issues. Some ODA data providers, such as the JDBC ODA plugin, may need
to in turn load various user specified JDBC drivers. We recognize that
it is not always convenient to require one to edit its plugin manifest
to specify additional JDBC jar files. We are looking into ways to
simplify the process of making additional JDBC drivers available to
BIRT. Watch for more details in the near future.
Linda
and BIRT Data Engine team
|
|
|
| Re: ODA Drivers Configuration - Retiring odaconfig.xml [message #26198 is a reply to message #25667] |
Tue, 12 April 2005 14:01  |
| Eclipse User |
|
|
|
Originally posted by: mbatchelor.no_s_p_a_m.pentaho.com
I've been unable to get the runtime workbench to pick up my mysql jar file.
No matter what I do, the only driver available to me when I create a new
JDBC Datasource is the JDBC/ODBC driver (the one available by default). I've
tried the following:
a- Modified the org.eclipse.birt.report.data.oda.jdbc plugin.xml as follows:
<runtime>
<library name="oda-jdbc.jar">
<export name="*"/>
</library>
<library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
<export name="*"/>
</library>
</runtime>
(Of course, I created the org.eclipse.birt.report.data.oda.jdbc\lib
directory and copied the .jar there).
b- Striking out there, I then did something similar in the
org.eclipse.birt.data.oda plugin.xml as follows:
<runtime>
<library name="oda.jar">
<export name="*"/>
</library>
<library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
<export name="*"/>
</library>
</runtime>
(Of course, I created the org.eclipse.birt.data.oda\lib directory and copied
the .jar there).
c- Again, running the runtime workbench, the only JDBC driver available to
me was the JDBC/ODBC driver. So, I then tried modifying the
org.eclipse.birt.data plugin.xml in the same way. Again, no dice.
d- Then, I decided to try adding it to the bootpath with the following
statement:
-Xbootclasspath/a:D:/japps/birtsrc/org.eclipse.birt.data/lib /mysql-connector
-java-3.0.16-ga-bin.jar
Again, no joy. It seems that, with this new architecture, I'm unclear how to
get your jdbc driver to appear as a choice when creating a datasource. What
am I missing???
"Linda Chan" <lchan@actuate.com> wrote in message
news:425AC184.369D4A3E@actuate.com...
> In response to the feedback we received from the community, we are
> moving an ODA driver's configuration info from its own file
> (odaconfig.xml) to its Eclipse plugin manifest.
>
> The two ODA drivers included in BIRT (jdbc and flatfile) have migrated
> to this new ODA plugin implementation. See their plugin.xml for
> examples on how the configuration info are now specified.
> The ODA runtime driver extension point schema can be found in CVS BIRT
> source tree: org.eclipse.birt.data.oda/schema/odaDriverRuntime.exsd.
> Use the Eclipse PDE Tools to see its reference document. Most elements
> that used to be in the odaconfig.xsd are now defined directly in the
> extension point schema.
>
> As part of this change, the ODA run-time framework no longer directly
> provides a separate URLClassLoader to load each ODA driver's library
> files (specified in <DriverLibraries> in the odaconfig.xml ). Instead,
> an ODA driver's class loading in the Eclipse environment is now
> delegated to the Eclipse class loading framework via OSGi. Therefore,
> the list of run-time library files are now specified in the <runtime>
> element in the ODA runtime extension's plugin.xml.
>
> In the BIRT Viewer application environment, the server class loading
> framework currently uses a single class loader to load all plug ins.
> What this means is that it cannot handle multiple ODA plugging that use
> conflicting versions of the same package. The class loading framework
> is being enhanced to fully adopt the Eclipse class loading behavior,
> e.g. use separate class loader for each plugin.
>
> Note that the above applies to the generic ODA run-time framework. We
> are looking into additional solution to address other ODA configuration
> issues. Some ODA data providers, such as the JDBC ODA plugin, may need
> to in turn load various user specified JDBC drivers. We recognize that
> it is not always convenient to require one to edit its plugin manifest
> to specify additional JDBC jar files. We are looking into ways to
> simplify the process of making additional JDBC drivers available to
> BIRT. Watch for more details in the near future.
>
> Linda
> and BIRT Data Engine team
>
|
|
|
| Re: ODA Drivers Configuration - Retiring odaconfig.xml [message #26239 is a reply to message #26198] |
Tue, 12 April 2005 14:33 |
| Eclipse User |
|
|
|
Originally posted by: mbatchelor.no_s_p_a_m.pentaho.com
Ok - after tracing in the source, it seems that you need to create a
directory called "drivers" underneath org.eclipse.birt.report.data.oda.jdbc,
and copy your JDBC drivers into there.
"Marc Batchelor" <mbatchelor@no_s_p_a_m.pentaho.com> wrote in message
news:d3h2od$57v$1@news.eclipse.org...
> I've been unable to get the runtime workbench to pick up my mysql jar
file.
> No matter what I do, the only driver available to me when I create a new
> JDBC Datasource is the JDBC/ODBC driver (the one available by default).
I've
> tried the following:
>
> a- Modified the org.eclipse.birt.report.data.oda.jdbc plugin.xml as
follows:
>
> <runtime>
> <library name="oda-jdbc.jar">
> <export name="*"/>
> </library>
> <library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
> <export name="*"/>
> </library>
> </runtime>
> (Of course, I created the org.eclipse.birt.report.data.oda.jdbc\lib
> directory and copied the .jar there).
>
> b- Striking out there, I then did something similar in the
> org.eclipse.birt.data.oda plugin.xml as follows:
>
> <runtime>
> <library name="oda.jar">
> <export name="*"/>
> </library>
> <library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
> <export name="*"/>
> </library>
> </runtime>
>
> (Of course, I created the org.eclipse.birt.data.oda\lib directory and
copied
> the .jar there).
>
> c- Again, running the runtime workbench, the only JDBC driver available to
> me was the JDBC/ODBC driver. So, I then tried modifying the
> org.eclipse.birt.data plugin.xml in the same way. Again, no dice.
>
> d- Then, I decided to try adding it to the bootpath with the following
> statement:
>
> -Xbootclasspath/a:D:/japps/birtsrc/org.eclipse.birt.data/lib /mysql-connect
or
> -java-3.0.16-ga-bin.jar
>
> Again, no joy. It seems that, with this new architecture, I'm unclear how
to
> get your jdbc driver to appear as a choice when creating a datasource.
What
> am I missing???
>
>
> "Linda Chan" <lchan@actuate.com> wrote in message
> news:425AC184.369D4A3E@actuate.com...
> > In response to the feedback we received from the community, we are
> > moving an ODA driver's configuration info from its own file
> > (odaconfig.xml) to its Eclipse plugin manifest.
> >
> > The two ODA drivers included in BIRT (jdbc and flatfile) have migrated
> > to this new ODA plugin implementation. See their plugin.xml for
> > examples on how the configuration info are now specified.
> > The ODA runtime driver extension point schema can be found in CVS BIRT
> > source tree: org.eclipse.birt.data.oda/schema/odaDriverRuntime.exsd.
> > Use the Eclipse PDE Tools to see its reference document. Most elements
> > that used to be in the odaconfig.xsd are now defined directly in the
> > extension point schema.
> >
> > As part of this change, the ODA run-time framework no longer directly
> > provides a separate URLClassLoader to load each ODA driver's library
> > files (specified in <DriverLibraries> in the odaconfig.xml ). Instead,
> > an ODA driver's class loading in the Eclipse environment is now
> > delegated to the Eclipse class loading framework via OSGi. Therefore,
> > the list of run-time library files are now specified in the <runtime>
> > element in the ODA runtime extension's plugin.xml.
> >
> > In the BIRT Viewer application environment, the server class loading
> > framework currently uses a single class loader to load all plug ins.
> > What this means is that it cannot handle multiple ODA plugging that use
> > conflicting versions of the same package. The class loading framework
> > is being enhanced to fully adopt the Eclipse class loading behavior,
> > e.g. use separate class loader for each plugin.
> >
> > Note that the above applies to the generic ODA run-time framework. We
> > are looking into additional solution to address other ODA configuration
> > issues. Some ODA data providers, such as the JDBC ODA plugin, may need
> > to in turn load various user specified JDBC drivers. We recognize that
> > it is not always convenient to require one to edit its plugin manifest
> > to specify additional JDBC jar files. We are looking into ways to
> > simplify the process of making additional JDBC drivers available to
> > BIRT. Watch for more details in the near future.
> >
> > Linda
> > and BIRT Data Engine team
> >
>
>
|
|
| |
| Re: ODA Drivers Configuration - Retiring odaconfig.xml [message #26500 is a reply to message #26239] |
Wed, 13 April 2005 16:16 |
| Eclipse User |
|
|
|
Hi Marc,
You are right on the bleeding edge of this area. ;-)
As described earlier, we are looking into ways to simplify the process of making
additional JDBC drivers available to BIRT. Getting the JDBC Designer UI to
display a selection list of additional JDBC drivers' class and URL falls into
this category. A solution is in the works, and should be available later this
week.
In the current state of implementation, you are correct that the JDBC Designer
UI only looks for JDBC jar files in a "drivers" sub-folder under the
org.eclipse.birt.report.data.oda.jdbc plugin.
BTW, your approach (a) in editing the oda.jdbc plugin.xml is correct.
The generic ODA run-time framework would indeed use the library file(s) listed
in the oda.jdbc plugin.xml.
> a- Modified the org.eclipse.birt.report.data.oda.jdbc plugin.xml as
follows:
>
> <runtime>
> <library name="oda-jdbc.jar">
> <export name="*"/>
> </library>
> <library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
> <export name="*"/>
> </library>
> </runtime>
Linda
Marc Batchelor wrote:
> Ok - after tracing in the source, it seems that you need to create a
> directory called "drivers" underneath org.eclipse.birt.report.data.oda.jdbc,
> and copy your JDBC drivers into there.
>
> "Marc Batchelor" <mbatchelor@no_s_p_a_m.pentaho.com> wrote in message
> news:d3h2od$57v$1@news.eclipse.org...
> > I've been unable to get the runtime workbench to pick up my mysql jar
> file.
> > No matter what I do, the only driver available to me when I create a new
> > JDBC Datasource is the JDBC/ODBC driver (the one available by default).
> I've
> > tried the following:
> >
> > a- Modified the org.eclipse.birt.report.data.oda.jdbc plugin.xml as
> follows:
> >
> > <runtime>
> > <library name="oda-jdbc.jar">
> > <export name="*"/>
> > </library>
> > <library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
> > <export name="*"/>
> > </library>
> > </runtime>
> > (Of course, I created the org.eclipse.birt.report.data.oda.jdbc\lib
> > directory and copied the .jar there).
> >
> > b- Striking out there, I then did something similar in the
> > org.eclipse.birt.data.oda plugin.xml as follows:
> >
> > <runtime>
> > <library name="oda.jar">
> > <export name="*"/>
> > </library>
> > <library name="lib/mysql-connector-java-3.0.16-ga-bin.jar">
> > <export name="*"/>
> > </library>
> > </runtime>
> >
> > (Of course, I created the org.eclipse.birt.data.oda\lib directory and
> copied
> > the .jar there).
> >
> > c- Again, running the runtime workbench, the only JDBC driver available to
> > me was the JDBC/ODBC driver. So, I then tried modifying the
> > org.eclipse.birt.data plugin.xml in the same way. Again, no dice.
> >
> > d- Then, I decided to try adding it to the bootpath with the following
> > statement:
> >
> > -Xbootclasspath/a:D:/japps/birtsrc/org.eclipse.birt.data/lib /mysql-connect
> or
> > -java-3.0.16-ga-bin.jar
> >
> > Again, no joy. It seems that, with this new architecture, I'm unclear how
> to
> > get your jdbc driver to appear as a choice when creating a datasource.
> What
> > am I missing???
> >
|
|
|
Goto Forum:
Current Time: Sat May 10 01:51:32 EDT 2025
Powered by FUDForum. Page generated in 0.04542 seconds |
Home