Oh, sorry, went to far ahead ;-). Sorry for the long explanations, but I don't want
to miss anything that might be relevant or trigger a memory.
Domain.XML
Store configured as:
======
<store name="tx2">
<parameter name="tlock-timeout">120</parameter>
<nodestore classname="org.apache.slide.store.txfile.TxXMLFileDescriptorsStore">
<parameter name="rootpath">e:/store/metadata</parameter>
<parameter name="workpath">worktx2/metadata</parameter>
<parameter name="defer-saving">true</parameter>
<parameter name="timeout">120</parameter>
</nodestore>
......
======
With scope configured as:
=====
<scope match="/store78" store="tx2"/>
=====
Will cause a file called 'store78.def.xml' to be created in the [EMAIL
PROTECTED]/nodestore/[EMAIL PROTECTED] value of "e:/store/metadata". I can not change
where 'store78.def.xml' is created without changing where all of the WebDAV file
metadata is saved.
'store78.def.xml' file looks like this:
========
<?xml version="1.0" encoding="UTF-8"?>
<data>
<objectnode classname="org.apache.slide.structure.SubjectNode" uri="/store78">
<children />
<parents>
<parent name="store78" uuri="/" />
</parents>
<links />
</objectnode>
<permissions>
<permission subjectUri="unauthenticated" actionUri="all" inheritable="true"
negative="false" />
</permissions>
<locks />
<revisionsHistory initialRevision="1.0" useVersioning="false">
<branches>
<branch name="main" lastestRevision="1.0" />
</branches>
<revisions>
<branch start="1.0" />
</revisions>
</revisionsHistory>
<descriptor>
<revisions branchName="main" number="1.0">
<labels />
<properties>
<property name="modificationdate" namespace="DAV:"
value="2004-10-11T17:47:57Z" type="" protected="true">
<permissions />
</property>
<property name="resourcetype" namespace="DAV:" value="<collection/>"
type="" protected="true">
<permissions />
</property>
<property name="source" namespace="DAV:" value="" type="" protected="true">
<permissions />
</property>
<property name="displayname" namespace="DAV:" value="store78" type=""
protected="false">
<permissions />
</property>
<property name="getlastmodified" namespace="DAV:" value="Mon, 11 Oct 2004
17:47:57 GMT" type="" protected="true">
<permissions />
</property>
<property name="creationdate" namespace="DAV:" value="2004-10-11T17:47:57Z"
type="" protected="true">
<permissions />
</property>
<property name="getcontentlength" namespace="DAV:" value="0" type=""
protected="true">
<permissions />
</property>
<property name="modificationuser" namespace="DAV:" value="unauthenticated"
type="" protected="true">
<permissions />
</property>
</properties>
</revisions>
</descriptor>
</data>
==============
For someone that uses a store/nodestore = database, where does this data get saved?
-D
> -----Original Message-----
> From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 12, 2004 4:46 PM
> To: Slide Users Mailing List
> Subject: Re: read-only support (CD/DVD)
>
>
> Could you define what the values of a scope are? This is what
> I do not
> understand...
>
> Oliver
>
> Darren Hartford schrieb:
> > This is the big question. I don't think it is.
> >
> > If in domain.xml, if you have a
> /slide/namespace/definition/store/nodestore configured as:
> > ===
> > <nodestore
> classname="org.apache.slide.store.txfile.TxXMLFileDescriptorsStore">
> > <parameter name="rootpath">store/metadata</parameter>
> > <parameter name="workpath">work/metadata</parameter>
> > <parameter name="defer-saving">true</parameter>
> > <parameter name="timeout">120</parameter>
> > </nodestore>
> > ===
> > My understanding is that /slide/namespace/definition/scope
> will save it's values under the nodestore configuration of
> the referenced <store>. If you have a <store> configured for
> nodestore=TxXMLFileDescriptorsStore, I don't think you can
> have the /definition/scope values stored in a database, or vice-versa.
> >
> > <scope> uses the referenced <store>'s nodestore
> configuration for saving it's values. <scope> does not have
> its own 'scopestore' to configure.
> >
> > As an example, security has its own SecurityStore that can
> be configured independently of <store>'s nodestore
> configuration. Adding <scope> to the SecurityStore or
> creating a new 'ScopeStore' (or ConfigStore) could be one
> workaround. Since the <scope>'s have to be unique, having a
> central store for all <scope> information for each namespace
> makes sense, regardless of the number of <store>'s.
> >
> >
> >
> >>-----Original Message-----
> >>From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
> >>Sent: Tuesday, October 12, 2004 4:18 PM
> >>To: Slide Users Mailing List
> >>Subject: Re: read-only support (CD/DVD)
> >>
> >>
> >>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:
> >>
> >
> >
> >
> ---------------------------------------------------------------------
> > 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]
