OK, I am confused. I thouht scope *is* independent of the store
definition, isn't it? Could you explain for me?
Oliver
Darren Hartford schrieb:
Maybe I'm thinking too simply, still new to Slide. As I look at it, you configure a <store>
first. The <store> may not yet exist, or it may already exist, you simply configure in
domain.xml to let it know the configuration, location, and other parameters about the store
(irregardless if it is TxFile/TxXML/DB-oriented/XMLDB/etc.).
Once you have a configured <store>, you need to add <scope> to that store. This seems to be a seperate
configuration that could/should be seperated out, but currently it is 100% dependent on the configuration of the
<store> as this is where you save the configuration defined in <scope>. My recommendation is to allow
<scope> to be independent of the <store> implementation/configuration.
Another way to look at it is similar to the J2EE/JNDI approach - the <store> is configured, has
parameters, and may be anything you setup. Then, you create a reference (similar to a JNDI reference)
called the STORENAME. The STORENAME itself has no meaning other than to point to the configuration and
parameters underneath it. <scope> uses this STORENAME reference for configuration of a different
'container', the actual URI mappings. Then, a step further, any <scope> parameters and
configurations are referenced by the SCOPEURI (the 'match' attribute) for the data/objectnode section
(or 'container').
sillypicture:
|store|--storename--|scope|--scopeuri--|data/objectnode|
But, the present problem is that the scope is not independent of the store, per the issue with
read-only configured stores. Basically, looking for an independent mechanism to configure
<scope> *without* depending on the <store> configuration (but, of course, still allow
it as the default option for backward compatibility).
Hope this thought process makes sense, I may be completely wrong though!
-D
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
