Re: [dba-dev] Sample Extension for Packaging ODB files

> (I hope responding to myself is not considered talking to myself ...) > Some more insights ... (this becomes a habit, it seems) > Sadly, *removing* the bibliography's node is not prevented by its > "finalized" attribute. Need to check whether this is intentional. Looking at the .xsd, it seems

Re: [dba-dev] read-only configuration data - unremoveable set nodes?

Frank Schönheit - Sun Microsystems Germany wrote: > Hi, this should have gone to [EMAIL PROTECTED], not [EMAIL PROTECTED] - sorry. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.

[dba-dev] read-only configuration data - unremoveable set nodes?

Hi, in the file backend of our configuration data (vulgo: the .xcu files in the [user|share]/registry/data/* folder hierarchy), it is possible to declare a configuration node, and all sub nodes, as read-only by adding the attribute "oor:finalized='true'". org/openoffice/Office/Paths.xcu and org/op

Re: [dba-dev] Sample Extension for Packaging ODB files

Frank Schönheit - Sun Microsystems Germany escribió: Hi Ariel, my somewhat unsorted thoughts on this in the late evening, I might detail this tomorrow. In general, we need to establish a codex for extensions - the layer structure you cited is open for extensions, and will continue to be, so the

Re: [dba-dev] Sample Extension for Packaging ODB files

Hi Drew, Drew Jensen escribió: Hi Ariel, I've been following along with your posts - one comment. About whether an extension supplied database should: a) be registered b) show up in the DSB I think this needs to be narrowly defined. If we are talking about actual odb files embedded in the

Re: [dba-dev] Sample Extension for Packaging ODB files

(I hope responding to myself is not considered talking to myself ...) Some more insights ... > - declaring config nodes as read-only must work at all This seems to work, somehow: Adding "ooo:finalized='true'" to the Name property of the Bibliography registration, in the share layer, prevents me

Re: [dba-dev] Sample Extension for Packaging ODB files

Hi Ariel, my somewhat unsorted thoughts on this in the late evening, I might detail this tomorrow. In general, we need to establish a codex for extensions - the layer structure you cited is open for extensions, and will continue to be, so they will be able to add own content to the DataAccess.xcu

Re: [dba-dev] Sample Extension for Packaging ODB files

Hi Ariel, I've been following along with your posts - one comment. About whether an extension supplied database should: a) be registered b) show up in the DSB I think this needs to be narrowly defined. If we are talking about actual odb files embedded in the oxt file, then I can see an argum

Re: [dba-dev] Sample Extension for Packaging ODB files

Hello Frank, after testing and thinking during the weak end I came to some conclusions. I think that there are several issues/RFE/features involved in this subject, so I didn't fill yet any issue: instead I'd like to share my point here and get your feedback. What is obviously an issue (type

Re: [dba-dev] UNOized Copy Table Wizard - snapshot release

Hi Ariel, > Only one little enhancement: after the call to > createWithInteractionHandler() the interaction dialog is executed, as I > forgot to add to the classpath of this dev. version the MySQL JDBC > driver, I got an exception, but it was just a > "com.sun.star.lang.WrappedTargetException:

Re: [dba-dev] UNOized Copy Table Wizard - snapshot release

Hi Ariel, >> first: of course I read the API! it's just that these questions are not >> answered there (at least for my understanding :-( ; for example in the >> description for the param. Destination of the constructor, it is not >> clear that there MUST be an ODB). > > Ooops, you're right,