| Suggestion for ODACONFIG.XML [message #24013] |
Thu, 31 March 2005 10:39  |
Eclipse User |
|
|
|
Right now odaconfig.xml contains the following:
<RunTimeInterface>
<InterfaceType>Java</InterfaceType>
<DriverInitEntryPoint>org.eclipse.birt.report.data.oda.jdbc.JDBCConnectionFa
ctory</DriverInitEntryPoint>
<DriverLibraries>
<LibrariesForOS>
<OSType>All</OSType>
<LibraryName>oda-jdbc.jar</LibraryName>
</LibrariesForOS>
<SetJavaThreadContextClassLoader>false</SetJavaThreadContextClassLoader >
</DriverLibraries>
</RunTimeInterface>
I suggest adding under LibrariesForOS a new node LibraryDir as in the
following example
<RunTimeInterface>
<InterfaceType>Java</InterfaceType>
<DriverInitEntryPoint>org.eclipse.birt.report.data.oda.jdbc.JDBCConnectionFa
ctory</DriverInitEntryPoint>
<DriverLibraries>
<LibrariesForOS>
<OSType>All</OSType>
<LibraryName>oda-jdbc.jar</LibraryName>
</LibrariesForOS>
<LibrariesForOS>
<OSType>Windows</OSType>
<LibraryDir>c:\birt\jdbc</LibraryDir>
</LibrariesForOS>
<LibrariesForOS>
<OSType>LINUX</OSType>
<LibraryDir>/var/eclipse/birt/jdbc</LibraryDir>
</LibrariesForOS>
<SetJavaThreadContextClassLoader>false</SetJavaThreadContextClassLoader >
</DriverLibraries>
</RunTimeInterface>
Any jar file found in the library directory would then be added to the
library list as if it had been explicitly stated in a <LibraryName> node.
This would drastically simplify setup and configuration of birt.
|
|
|
|
| Re: Suggestion for ODACONFIG.XML [message #24281 is a reply to message #24238] |
Thu, 31 March 2005 19:24  |
| Eclipse User |
|
|
|
The biggest issue that I see is the relative complexity of providing BIRT to
only semi-technical people and still being able to provide different JDBC
drivers simply. Anything which would require editing a file found under
ECLIPSE_HOME would be a bad thing. I'd like to be able to provide BIRT to
our semi-technical people running under Eclipse platform, and to be able to
take full advantage of update sites to allow them to stay up-to-date. We
would need to be able to provide jdbc drivers for DB2/AS400, Oracle, and
MySQL What I would consider ideal would be the ability to create an eclipse
plugin which would contain a JDBC driver and register it into ODA. (In
fact, I've got some source code that does this - but it is from before a
couple of CVS reorganizations so I'd have to work through it again.)
From a runtime point of view, I'd like to have a BIRT service running under
Websphere, and it seems to me that a different type of additivity would be
needed for that. And I'd like to see that installation and configuration to
be as plug-and-play as possible also - ideally by deploying an ear file.
The primary intent of my suggestion was to be able to specify a directory
that JDBC driver jar files could be placed into without having to name the
jar files explicitly - very similar in concept to the way WEB-INF/lib
behaves for a servlet container. The same mechanism could have worked both
within Eclipse and in a BIRT servlet context.
"Linda Chan" <lchan@actuate.com> wrote in message
news:72b7ec5429d0c3b539ea5cb371829526$1@www.eclipse.org...
> Thierry,
>
> Thanks for the input.
>
> In the current odaconfig schema definition (located in the source tree
> under org.eclipse.birt.data/schema/ODAConfig.xsd ), the
> <LibrariesForOSType> includes an optional <Location> element. This is for
> the folder location of the files listed under <LibraryName>.
>
> With that said, the scheme is going to change though...
> In response to the feedback we received from the community, we plan to
> move the ODA driver configuration info to the Eclipse plugin manifest
> directly. The run-time libraries will be listed in an ODA extension
> plugin.xml's <runtime> element, and their class loading will be handled by
> the Eclipse class loading framework via OSGi.
> This feature is planned to be available in April.
> Any feedback on this planned enhancement will be much appreciated.
>
> Linda
>
|
|
|
Powered by
FUDForum. Page generated in 0.03804 seconds
Home