Hi Frank, > When the config data is created by OOo itself, then the node name and the > property value are identical.
yes, you are right, i tried to insert a more readable (localized) display name, but wasn't aware that oo 3.2 will use the "node name" for database access. so for upward compatibility i will change it back to the registration name ... otherwise our users's will have to use "Edit - Echange Database..." or even change macro code in oo 3.x ... thanks :-) Oliver Am 24.02.2010 09:56 schrieb Frank Schoenheit, Sun Microsystems Germany: > Hi Oliver, > >> Is it correct, that "oDatabaseContext.getElementNames()" will return the >> displayed name >> (shown in database brwoser) and not the "registered Name" shown in Tools - >> Options ? >> >> for example the macro below will return "My Database", not "mydatabase" >> >> <node oor:name="RegisteredNames"> >> <node oor:name="My Database" oor:op="replace"> >> <prop oor:name="Location" oor:type="xs:string"> >> <value>file:///X:/MyDatabase.odb</value> >> </prop> >> <prop oor:name="Name" oor:type="xs:string"> >> <value>mydatabase</value> >> </prop> >> </node> >> </node> > > The code for this happen[s/ed] to be a little ... inconsistent. When the > config data is created by OOo itself, then the node name and the > property value are identical. When reading the data, the node name is > taken as registration name. Strictly, this is wrong, of course, but it's > noticed only when the node name and the prop value are not identical. > > On the DEV300 code line, this has been fixed - now the property value is > taken as registration name, the node name can be an arbitrary logical > name (preferably something like "org.<something>" to ensure uniqueness). > > In addition, an interface css.sdb.XDatabaseRegistrations [1] has been > introduced, which hides the configuration data from you, so there is no > need to tamper with it directly (The exception would be an extension > bringing its own configuration data with it, but even here, an on-demand > registration using XDatabaseRegistrations and the new XDeploymentHook > would be possible). > > Ciao > Frank > > [1]http://hg.services.openoffice.org/DEV300/file/1467f46f8817/offapi/com/sun/star/sdb/XDatabaseRegistrations.idl > -- Oliver Brinzing fon +49 7181 481401 fax +49 7181 475635 Ludwigstrasse 14 mobil +49 174 3015743 73614 Schorndorf mailto:[email protected] GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45
signature.asc
Description: OpenPGP digital signature
