Very good to hear these news Ole. Regarding your question, does "create the LDAP type system" means creating the LDAP schema on the LDAP server ? Do you also have the scenario of updating the schema ? What about pre-populating like in sample applications ? Well, if you have these scenarios, maybe it would be better to use an utility to allow applications to do that, we have a similar thing in RDB DAS (dbConfig).
As for the other option, that you mentioned, are you always going to have access to the configFile ? In the case of RDB DAS, we allow for configuring only by passing a Stream, and in this case I guess you solution would fail. On 7/21/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Howdy, UPDATE: The LDAP DAS is reading and writing graphs and it can process the change summary. I still have a few more tests to write, but I think it's pretty solid. QUESTION: Right now I default the isTypeSystemCreated configuration parameters (Keyed by model namespaceURI) to false. If the DAS runs with it set this way, it will always attempt to create the LDAP type system, but will still check to see if it exists first. I'd like to automate setting it to true, after the DAS has run for the first time. One way would be to just rewrite the configuration file, and then read it again in order to validate the rewrite. Does this sound OK? Are there better ways? Thanks, - Ole --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
