[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
Oj, I had updated the scp2 module, both the files you mentioned. I also do a build --all after my changes which must have done the registration. I still cannot see my driver loaded; as I said it wont find my driver name org.openoffice.comp.connectivity.skeleton.SkeletonDriver in its list of names in OSDBCDriverManager::implGetDriverForURL function. Is there any way to debug this ? also for dbaccess code it have too many files with sdbc: what exactly am I looking for here ? thanks, Rohit On Wed, Mar 30, 2011 at 12:43 AM, Ocke Janssen ocke.jans...@oracle.comwrote: Hello Rohit, On 30.03.2011 03:01, Rohit Kulkarni wrote: Hello Oj, I an not writing the sdbcx driver, also I can debug everything else but my driver code. I am guessing I am not registering the driver properly. I have written the .xml file for the driver and also made changes to DataAccess.xcu. Should this be sufficient to register the driver? if not what else do I need to do ? Do have changed the module scp2 and added lines like STD_LIB_FILE(gid_File_Lib_Mysql,mysql) in file_library_ooo.scp and gid_File_Lib_Mysql, in module_hidden_ooo.scp ? You have to build OOo instset because your registration is done there. If the driver should not be an extension than we you could remove your dataaccess.xcu changes and adjust the code in dbaccess (look for sdbc: ) Best regards, oj Here are excerpts from those files: == DriverSkeleton.xml ?xml version='1.0' encoding=UTF-8? !DOCTYPE COMPONENTDESCRIPTION PUBLIC -//W3C//DTD HTML 3.2//EN module-description.dtd module-description xmlns:xlink=http://www.w3.org/1999/xlink; module-name skeleton1 /module-name component-description Authorrohit/Author Nameorg.openoffice.comp.connectivity.skeleton.SkeletonDriver/Name descriptionThis library implements the database driver for Skeleton./description loader-namecom.sun.star.loader.SharedLibrary/loader-name languagec++/language status value=alpha/ supported-servicecom.sun.star.sdbc.Driver/supported-service service-dependency... /service-dependency /component-description project-build-dependencycppuhelper/project-build-dependency project-build-dependencycppu/project-build-dependency project-build-dependencysal/project-build-dependency project-build-dependencyvos/project-build-dependency runtime-module-dependencycppuhelper/runtime-module-dependency runtime-module-dependencycppu1/runtime-module-dependency runtime-module-dependencysal1 /runtime-module-dependency runtime-module-dependencyvos/runtime-module-dependency /module-description = DataAccess.xcu = !DOCTYPE oor:component-data SYSTEM ../../../../component-update.dtd oor:component-data oor:name=DataAccess oor:package=org.openoffice.Office xmlns:oor=http://openoffice.org/2001/registry; xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; node oor:name=UserDefinedDriverSettings node oor:name=Driver Skeleton oor:op=replace prop oor:name=DriverTypeDisplayName valueDriver Skeleton/value /prop prop oor:name=DriverPageDisplayName valueDriver Skeleton Page/value /prop prop oor:name=DriverDsnPrefix valuesdbc:skeleton:/value /prop /node /node node oor:name=ConnectionPool node oor:name=DriverSettings node oor:name=org.openoffice.comp.connectivity.skeleton.SkeletonDriver oor:op=replace prop oor:name=DriverName valueorg.openoffice.comp.connectivity.skeleton.SkeletonDriver/value /prop prop oor:name=Enable valuefalse/value /prop prop oor:name=Timeout value60/value /prop /node node oor:name=com.sun.star.comp.sdbcx.adabas.ODriver oor:op=replace prop oor:name=DriverName valuecom.sun.star.comp.sdbcx.adabas.ODriver/value /prop ... : -- there is also a DriverSkeleton.xcu as below: = DriverSkeleton.xcu = oor:component-data oor:name=Drivers oor:package=org.openoffice.Office.DataAccess xmlns:oor=http://openoffice.org/2001/registry; xmlns:xs=http://www.w3.org/2001/XMLSchema; node oor:name=Installed node oor:name=sdbc:skeleton:* oor:op=replace prop oor:name=Driver valueorg.openoffice.comp.connectivity.skeleton.SkeletonDriver/value /prop prop oor:name=DriverTypeDisplayName oor:type=xs:string value xml:lang=en-USSkeleton Driver/value /prop node oor:name=Features node oor:name=EscapeDateTime oor:op=replace prop oor:name=Value oor:type=xs:boolean valuetrue/value /prop /node /node /node /node /oor:component-data as for this I have updated the build.lst and d.lst files so that it builds the libDriverSkeletonli.so file and copies it into the installation set. But when I debug this I can see that my driver is not returned as part of enumeration by createContentEnumeration() Could you suggest any way I can fix this? thanks in advance. -Rohit On Tue, Mar 29, 2011 at 12:06 AM, Ocke Janssen ocke.jans...@oracle.com mailto:ocke.jans...@oracle.com wrote: Hi Rohit,
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
Hi, On 26.03.2011 06:47, Rohit Kulkarni wrote: Hello, I have successfully built skeleton driver and I can see it in available list. Now , I tried to debug it using gdb. For this I followed instructions on http://wiki.services.openoffice.org/wiki/Debugging Build using debug=true and copied .so files to installation set. I added a breakpoint at connectivity::skeleton::SkeletonDriver::acceptsURL then, run base - select Skeleton Driver - Datasource url window appears (typed any string in it) - saved -finish In this process debugger wont stop at breakpoint. Another thing is that I added breakpoint at connectivity::flat::ODriver::acceptsURL then, all same steps above. Debugger stopped at breakpoint where I can see flat file EDriver.cxx code with acceptsURL function. So, do you have any idea why it wouldn't call connectivity::skeleton::SkeletonDriver::acceptsURL function? May be you copied the wrong files or you built them not with debug=t ? When you can set a break point for flat it should also work for your driver. No guess so far. Or may be set the break point when the library was loaded. I'm not the gdb expert. - oj Regards, Rohit On Tue, Mar 15, 2011 at 11:53 AM, Ocke Janssen ocke.jans...@oracle.com mailto:ocke.jans...@oracle.com wrote: On 14.03.2011 18:45, Rohit Kulkarni wrote: I could successfully built the skeleton driver and now I can see it in the list of available drivers as well! Thanks a lot for your help. I really appreciate it. :-) I have a quick question. Any idea on how to solve this? No, sorry. I think that's a question for the normal d...@openoffice.org mailto:d...@openoffice.org list. May be a build problem or a bug. Also, Now, if I make any changes to the skeleton driver, do I have to build and install open office every time? No, just replace your copy of the .so file in your office installation. - oj -- Ocke Janssen | Software Developer Phone: +40 23646500 Oracle Office ORACLE Deutschland B.V. Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Rijnzathe 6, 3454PV De Meern, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven Oracle is committed to developing practices and products that help protect the environment -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org mailto:dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org mailto:sy...@dba.openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
Hi Rohit, On 28.03.2011 17:43, Rohit Kulkarni wrote: Hello, 1) I built whole openoffice and installed it.(normal build i.e build --all) 2) I built only dbaccess and connectivity modules with debug=true dbglevel=2 3) Copied .so files from ../connectivity/unxlngi6.pro/lib/* http://unxlngi6.pro/lib/* and ../dbaccess/unxlngi6.pr/lib/* http://unxlngi6.pr/lib/* to ../../openoffice3/basis-link/program/ 4) Now I set breakpoint to b connectivity::flat::ODriver::acceptsURL 5) Run base through gdb. 6) Execution stopped at breakpoint, whatever I select flat or skeleton driver or any other from available driver list. 7) When I set breakpoint at b connectivity::skeleton::SkeletonDriver::acceptsURL , it wont stop at breakpoint. 8) That means execution of program never goes to SDriver.cxx (skeleton driver file) file which has acceptsURL function. The things I have noticed after some more debugging in gdb are -- 1) I saw the function named OSDBCDriverManager::bootstrapDrivers() 2) I think this is the function where it populates the list of all drivers using createContentEnumeration function. 3) And this function is not returning my driver. 4) I saw this after watching the value of aDriverDescriptor variable which is used for pushback in vector m_aDriverBS , I saw various strings for example , for flat it is com.sun.star.comp.sdbc.flat.ODriver but not my driver name. What do I need to do so that createContentEnumeration will return my driver object in the list ? Do you register the driver as an extension? If so the lib are not located in basis-link/program they are located in your user folder 3/user/uno_package/cache/uno_package/... That would also explain why you can't set any breakpoint. Another reason could be that your driver doesn't support com.sun.star.sdbc.Driver or the driver was not registered. If that doesn't work I could look at the code if you want to. Best regards, Ocke Regards, Rohit On Mon, Mar 28, 2011 at 1:16 PM, Ocke Janssen ocke.jans...@oracle.com mailto:ocke.jans...@oracle.com wrote: Hi, On 26.03.2011 06:47, Rohit Kulkarni wrote: Hello, I have successfully built skeleton driver and I can see it in available list. Now , I tried to debug it using gdb. For this I followed instructions on http://wiki.services.openoffice.org/wiki/Debugging Build using debug=true and copied .so files to installation set. I added a breakpoint at connectivity::skeleton::SkeletonDriver::acceptsURL then, run base - select Skeleton Driver - Datasource url window appears (typed any string in it) - saved -finish In this process debugger wont stop at breakpoint. Another thing is that I added breakpoint at connectivity::flat::ODriver::acceptsURL then, all same steps above. Debugger stopped at breakpoint where I can see flat file EDriver.cxx code with acceptsURL function. So, do you have any idea why it wouldn't call connectivity::skeleton::SkeletonDriver::acceptsURL function? May be you copied the wrong files or you built them not with debug=t ? When you can set a break point for flat it should also work for your driver. No guess so far. Or may be set the break point when the library was loaded. I'm not the gdb expert. - oj Regards, Rohit On Tue, Mar 15, 2011 at 11:53 AM, Ocke Janssen ocke.jans...@oracle.com mailto:ocke.jans...@oracle.com mailto:ocke.jans...@oracle.com mailto:ocke.jans...@oracle.com wrote: On 14.03.2011 18:45, Rohit Kulkarni wrote: I could successfully built the skeleton driver and now I can see it in the list of available drivers as well! Thanks a lot for your help. I really appreciate it. :-) I have a quick question. Any idea on how to solve this? No, sorry. I think that's a question for the normal d...@openoffice.org mailto:d...@openoffice.org mailto:d...@openoffice.org mailto:d...@openoffice.org list. May be a build problem or a bug. Also, Now, if I make any changes to the skeleton driver, do I have to build and install open office every time? No, just replace your copy of the .so file in your office installation. - oj -- Ocke Janssen | Software Developer Phone: +40 23646500 Oracle Office ORACLE Deutschland B.V. Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München,
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
I could successfully built the skeleton driver and now I can see it in the list of available drivers as well! Thanks a lot for your help. I really appreciate it. I have a quick question. When I build OOO, I have to run the installation step as cd instsetoo_native/util dmake openoffice_en-US PKGFORMAT=installed to install the ooo build. While installing the ooo I am getting following error ... merging files into registry database ... ... analyzing all directories for this product ... ... analyzing links ... ... analyzing unix links ... ... creating profiles ... ... analyzing modules ... ... creating installation directory ... ... creating installation set in /home/rohitiskul/ooo/OOO320_m19/instsetoo_native/ unxlngi6.pro/OpenOffice/installed/install/en-US ... ... removing old installation directories ... ... creating directories ... ... copying files ... ... creating links ... ... registering extensions ... ... current dir: /home/rohitiskul/ooo/OOO320_m19/instsetoo_native/ unxlngi6.pro/OpenOffice/installed/install/en-US_inprogress/openoffice.org3/program... ... unopkg add --shared --suppress-license --verbose ../share/extension/install/dict-en.oxt -env:UserInstallation=file:///tmp/ooopackaging/i_231461300204492/ unxlngi6.pro/OpenOffice/installed/uno/en-US 21 | ... ... cleaning the output tree ... ... removing directory /tmp/ooopackaging/i_231461300204492 ... ... removing directory /home/rohitiskul/ooo/OOO320_m19/instsetoo_native/ unxlngi6.pro/OpenOffice/installed/stripped/en-US ... ** ERROR: ERROR: unopkg add --shared --suppress-license --verbose ../share/extension/install/dict-en.oxt -env:UserInstallation=file:///tmp/ooopackaging/i_231461300204492/ unxlngi6.pro/OpenOffice/installed/uno/en-US 21 | failed! in function: register_extensions ** ** ERROR: Saved logfile: /home/rohitiskul/ooo/OOO320_m19/instsetoo_native/ unxlngi6.pro/OpenOffice/installed/logging/en-US/log_OOO320_en-US.log ** Tue Mar 15 21:31:10 2011 (06:18 min.) dmake: Error code 255, while making 'openoffice_en-US.installed' Any idea on how to solve this? Also, Now, if I make any changes to the skeleton driver, do I have to build and install open office every time? Thanks, Rohit On Mon, Mar 14, 2011 at 12:55 PM, Ocke Janssen ocke.jans...@oracle.comwrote: Hi Rohit, On 12.03.2011 07:17, Rohit Kulkarni wrote: As a first step, I copied the folder DriverSkeleton to ../connectivity/drivers/ .I created .xcu and .xml files.To run dmake I must have makefile.mk http://makefile.mk in my driver folder. So, I checked a makefile.mk http://makefile.mk in calc folder and made same for DriverSkeleton driver. Also, I copied exports.dxp and .map files from calc to DriverSkeleton. Finally, my DriverSkeleton folder contains following files-- [root@localhost drivers]# cd DriverSkeleton/ [root@localhost DriverSkeleton]# ls DriverSkeleton.map Makefile propertyids.hxxSDriver.cxx SResultSet.hxxSStatement.hxx DriverSkeleton.xcu makefile.mk http://makefile.mk SConnection.cxx SDriver.hxx SResultSetMetaData.cxx DriverSkeleton.xml OSubComponent.hxxSConnection.hxx SPreparedStatement.cxx SResultSetMetaData.hxx exports.dxp OTypeInfo.hxx SDatabaseMetaData.cxx SPreparedStatement.hxx SServices.cxx How_to_write_my_own_driver.txt propertyids.cxx SDatabaseMetaData.hxx SResultSet.cxx SStatement.cxx Delete following files they are not longer needed because they already exists in the connectivity module. - Makefile (you replaced it with makefile.mk) - propertyids.cxx, propertyids.hxx, OTypeInfo.hxx (these files are located in connectivity/source/inc) Please rename you xcu and xml file to a more explaining name like VeryFastLdapDriver, just kidding but you should use a better name than DriverSkeleton.xcu or xml :-) The name has to be unique as well as the cxx files. Best regards, Ocke After running dmake in the same folder it give me the following output-- ../../../unxlngi6.pro/slo/SResultSet.o http://unxlngi6.pro/slo/SResultSet.o: In function `connectivity::skeleton::OResultSet::createArrayHelper() const': SResultSet.cxx:(.text+0x439): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x49d): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x501): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x55f): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x5c3): undefined reference to
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
As a first step, I copied the folder DriverSkeleton to ../connectivity/drivers/ .I created .xcu and .xml files.To run dmake I must have makefile.mk in my driver folder. So, I checked a makefile.mk in calc folder and made same for DriverSkeleton driver. Also, I copied exports.dxp and .map files from calc to DriverSkeleton. Finally, my DriverSkeleton folder contains following files-- [root@localhost drivers]# cd DriverSkeleton/ [root@localhost DriverSkeleton]# ls DriverSkeleton.map Makefile propertyids.hxxSDriver.cxx SResultSet.hxxSStatement.hxx DriverSkeleton.xcu makefile.mk SConnection.cxx SDriver.hxx SResultSetMetaData.cxx DriverSkeleton.xml OSubComponent.hxxSConnection.hxx SPreparedStatement.cxx SResultSetMetaData.hxx exports.dxp OTypeInfo.hxx SDatabaseMetaData.cxx SPreparedStatement.hxx SServices.cxx How_to_write_my_own_driver.txt propertyids.cxx SDatabaseMetaData.hxx SResultSet.cxx SStatement.cxx After running dmake in the same folder it give me the following output-- ../../../unxlngi6.pro/slo/SResultSet.o: In function `connectivity::skeleton::OResultSet::createArrayHelper() const': SResultSet.cxx:(.text+0x439): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x49d): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x501): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x55f): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SResultSet.cxx:(.text+0x5c3): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' ../../../unxlngi6.pro/slo/SResultSet.o:SResultSet.cxx:(.text+0x627): more undefined references to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' follow ../../../unxlngi6.pro/slo/SResultSet.o: In function `connectivity::skeleton::OResultSet::getMetaData()': SResultSet.cxx:(.text+0x1f9f): undefined reference to `vtable for connectivity::skeleton::OResultSetMetaData' ../../../unxlngi6.pro/slo/SResultSet.o: In function `connectivity::skeleton::OPropertyMap::getPropMap()': SResultSet.cxx:(.text._ZN12connectivity8skeleton12OPropertyMap10getPropMapEv[connectivity::skeleton::OPropertyMap::getPropMap()]+0x9b): undefined reference to `connectivity::skeleton::OPropertyMap::~OPropertyMap()' ../../../unxlngi6.pro/slo/SStatement.o: In function `connectivity::skeleton::OStatement_Base::createArrayHelper() const': SStatement.cxx:(.text+0x58d): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SStatement.cxx:(.text+0x5f1): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SStatement.cxx:(.text+0x658): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SStatement.cxx:(.text+0x6bf): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' SStatement.cxx:(.text+0x726): undefined reference to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' ../../../unxlngi6.pro/slo/SStatement.o:SStatement.cxx:(.text+0x78d): more undefined references to `connectivity::skeleton::OPropertyMap::getNameByIndex(long) const' follow ../../../unxlngi6.pro/slo/SPreparedStatement.o: In function `connectivity::skeleton::OPreparedStatement::getMetaData()': SPreparedStatement.cxx:(.text+0xc05): undefined reference to `vtable for connectivity::skeleton::OResultSetMetaData' collect2: ld returned 1 exit status dmake: Error code 1, while making '../../../ unxlngi6.pro/lib/libDriverSkeletonli.so' I am building the Skeleton Driver and I dont know how to solve this problem. Could you please help to solve this problem? Am I doing anything wrong ? Thanks, Rohit On Fri, Mar 11, 2011 at 11:35 AM, Ocke Janssen ocke.jans...@oracle.comwrote: Hi Rohit, On 10.03.2011 16:58, Rohit Kulkarni wrote: Hi, Thanks for your reply. I really appreciate the help. I could find the skeleton files at the location you have mentioned. Currently we are planning to develop the SDBC driver which will not be an extension. So, we will have to build the skeleton driver first, get it in the list of available drivers and then make it work for LDAP. Could you please elaborate the point where you mentioned to search for macab key on the website? How does the open office dmake understand that it has to build this new driver? I guess you place your driver in connectivity. So in that module you find a file named prj/build.lst that is read when call the build command. But for the start you could simply go in your folder and call dmake. Each driver has a xcu file which must be delivered. Which files are needed to
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
Hi, Thanks for your reply. I really appreciate the help. I could find the skeleton files at the location you have mentioned. Currently we are planning to develop the SDBC driver which will not be an extension. So, we will have to build the skeleton driver first, get it in the list of available drivers and then make it work for LDAP. Could you please elaborate the point where you mentioned to search for macab key on the website? How does the open office dmake understand that it has to build this new driver? Thanks, Rohit On Thu, Mar 10, 2011 at 12:38 PM, Ocke Janssen ocke.jans...@oracle.comwrote: Hi Rohit, First of all you have to decide if the driver should be an extension or not. I would first try it as extension because you could look at the mysql driver. Not an extension: The best and easiest way to start I guess is to simply copy the skeleton files in a folder beside the other database drivers in connectivity. Further on you should copy e.g. the macab.xml and macab.xcu file and rename it to your driver in the same directory. Search with opengrok http://svn.services.openoffice.org/opengrok/ the macab key inside the other projects e.g. scp2 to include the files into the OOo installation. Build OOo. As extension: Here the best way is to look at the mysqlc/source where the mysql extension is build and copy the files you need to build the oxt. But please be aware to replace all occurrences of mysql with your name ;-) Best regards, Ocke On 09.03.2011 19:21, Ocke Janssen wrote: Hi, The driver can be found here ooo\odk\examples\DevelopersGuide\Database\DriverSkeleton - oj PS: I'll write more tomorrow. ;-) On 09.03.2011 16:37, Rohit Kulkarni wrote: Currently I am writing an SDBC driver for LDAP directories. I am following the guidelines given at http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/SDBC_Driver This includes writing Driver, connection, statement and resultset services. I want to compile the skeleton driver code and have an entry in the list of available drivers. This driver will be a pseudo driver and will not have any functionality. This will help in developing the actual driver. I am not able to find skeleton driver related source files. I could locate a folder named skeleton in /OOO320_m19/connectivity/workben/skeleton but could not find actual source files. Could anyone please give me any pointers regarding 1. Where can I find the source files for the skeleton driver? 2. How to build a skeleton driver? 3. How to make an entry in available drivers list? Thanks for your time. I really appreciate the help. Regards, Rohit -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
Hi, The driver can be found here ooo\odk\examples\DevelopersGuide\Database\DriverSkeleton - oj PS: I'll write more tomorrow. ;-) On 09.03.2011 16:37, Rohit Kulkarni wrote: Currently I am writing an SDBC driver for LDAP directories. I am following the guidelines given at http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/SDBC_Driver This includes writing Driver, connection, statement and resultset services. I want to compile the skeleton driver code and have an entry in the list of available drivers. This driver will be a pseudo driver and will not have any functionality. This will help in developing the actual driver. I am not able to find skeleton driver related source files. I could locate a folder named skeleton in /OOO320_m19/connectivity/workben/skeleton but could not find actual source files. Could anyone please give me any pointers regarding 1. Where can I find the source files for the skeleton driver? 2. How to build a skeleton driver? 3. How to make an entry in available drivers list? Thanks for your time. I really appreciate the help. Regards, Rohit -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help
[dba-dev] Re: Help Required In Writing a New SDBC Driver For LDAP
Hi Rohit, First of all you have to decide if the driver should be an extension or not. I would first try it as extension because you could look at the mysql driver. Not an extension: The best and easiest way to start I guess is to simply copy the skeleton files in a folder beside the other database drivers in connectivity. Further on you should copy e.g. the macab.xml and macab.xcu file and rename it to your driver in the same directory. Search with opengrok http://svn.services.openoffice.org/opengrok/ the macab key inside the other projects e.g. scp2 to include the files into the OOo installation. Build OOo. As extension: Here the best way is to look at the mysqlc/source where the mysql extension is build and copy the files you need to build the oxt. But please be aware to replace all occurrences of mysql with your name ;-) Best regards, Ocke On 09.03.2011 19:21, Ocke Janssen wrote: Hi, The driver can be found here ooo\odk\examples\DevelopersGuide\Database\DriverSkeleton - oj PS: I'll write more tomorrow. ;-) On 09.03.2011 16:37, Rohit Kulkarni wrote: Currently I am writing an SDBC driver for LDAP directories. I am following the guidelines given at http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/SDBC_Driver This includes writing Driver, connection, statement and resultset services. I want to compile the skeleton driver code and have an entry in the list of available drivers. This driver will be a pseudo driver and will not have any functionality. This will help in developing the actual driver. I am not able to find skeleton driver related source files. I could locate a folder named skeleton in /OOO320_m19/connectivity/workben/skeleton but could not find actual source files. Could anyone please give me any pointers regarding 1. Where can I find the source files for the skeleton driver? 2. How to build a skeleton driver? 3. How to make an entry in available drivers list? Thanks for your time. I really appreciate the help. Regards, Rohit -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help -- - To unsubscribe send email to dev-unsubscr...@dba.openoffice.org For additional commands send email to sy...@dba.openoffice.org with Subject: help
