James Mason schrieb:
I don't think I'm completely clear on the issue, so I'll try to summarize how I understand this.
When an existing Tx* store is moved to a different scope the name of the "root" def.xml file changes to match the name of the new scope. When the
I do not think so, does it?
filesystem of the existing store is read-only (as on a CD) this can't happen and the store is not loaded. The suggestion is to add a parameter to the <scope> element in the namespace to specify where the Tx* store should put the "root" descriptor file.
Assuming that my summary is correct (and I really feel like I'm missing something) I think the parameter would be more appropriate in the configuration of the TxXMLFileDescriptorsStore. I can't see how different store implementations would be able to use the parameter, and putting it with the <scope> implies it is some sort of generally-applicable value.
Other than that it seems like a good idea to me :). I haven't worked on the Tx* stores at all, though, so there could be implications here that I'm unaware of.
Maybe I got it all wrong (again), but this is how I understood it: roots of a store that is mapped with the scope element get a write request upon initialization which failed for Darren as his store is read-only. Now, there might be a flag telling Slide not to write to it. I was thinking of a read-only flag for a full scope.
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
