You want to store only the metadata in a customized way. Right?

Than you have to implement the interfaces
  RevisionDescriptorStore,
  RevisionDescriptorsStore and
  optionally NodeStore.

In RevisionDescriptorStore you has to manage NodeRevisionDescriptor objects in your
custom way. NodeRevisionDescriptor are the container of the metadata.

The ObjectStore manages the directory structure is this is part of your metadata
that you have to implement this too.

If you really doesn't want to use versioning the RevisionDescriptorsStore
implemenation is quite easy. retrieveRevisionDescriptors has to return a
almost constant object like the following

 public static final String DEFAULT_BRANCH_NAME = "main";
 public static final NodeRevisionNumber INITAL_REVISION_NUMBER
                                               = new NodeRevisionNumber(1, 0);

 public NodeRevisionDescriptors retrieveRevisionDescriptors(Uri uri)
      throws ServiceAccessException, RevisionDescriptorNotFoundException
 {

 // check whether the uri exists or throw ResourceNotFoundException

 Hashtable workingRevisions = new Hashtable();
 Hashtable latestRevisionNumbers = new Hashtable();
 Hashtable branches = new Hashtable();
 workingRevisions.put(DEFAULT_BRANCH_NAME, INITAL_REVISION_NUMBER);
 latestRevisionNumbers.put(DEFAULT_BRANCH_NAME, INITAL_REVISION_NUMBER);
 // initial revision with no successor
 branches.put(INITAL_REVISION_NUMBER, new Vector());

 return new NodeRevisionDescriptors(
     uri.toString(),
     INITAL_REVISION_NUMBER,
     workingRevisions,
     latestRevisionNumbers,
     branches,
     false                   // is not versioned
 );
}

The other methods of RevisionDescriptorsStore can remain empty.

You should also set org.apache.slide.versioncontrol=false in the
slide.properties file.

for locks and permissions you can use the TransientXXXStore implementations.

your domain.xml will look like

 <store name="myStore">
      <nodestore classname="org.apache.slide.store.txfile.TxXMLFileDescriptorsStore">
          <parameter name="rootpath">store/metadata</parameter>
          <parameter name="workpath">work/metadata</parameter>
      </nodestore>
      <contentstore classname="org.apache.slide.store.txfile.TxFileContentStore">
          <parameter name="rootpath">store/content</parameter>
          <parameter name="workpath">work/content</parameter>
      </contentstore>
      <revisiondescriptorsstore classname="your.RevisionDescriptorsStoreImpl">
      </revisiondescriptorsstore>
      <revisiondescriptorstore  classname="your.RevisionDescriptorStoreImpl">
      </revisiondescriptorstore>
      <securitystore classname="org.apache.slide.store.mem.TransientSecurityStore"/>
      <lockstore classname="org.apache.slide.store.mem.TransientLockStore"/>
 </store>

the nodestore you may replace by your own.

hope this helps
Stefan


Mihir Solanki wrote:
Hi all,



I am writing my own custom store. The basic requirement is as under.



1. Actual content should be created in some directory as per configured in Domain.xml

2. Descriptor records (metadata) should be created in the ORACLE database

3. No versioning, locking, permissions, ACL is required to be implemented.



I am using slide source code version 2.0.



Can anybody please guide me what all method I have to take care for the above requirements.

Is it possible to disable locking, permissions, ACLs etc of the slide.



One more thing I even don?t want to use the tables provided by slide, instead I would like to map

those tables and fields with my oracle db tables and fields.



Looking for the help on the above?.



Thanks,



Mihir



Sr. Software Engineer

SBU: eBiz, Gandhinagar



"Imaginations... its limits are only those of the mind itself"




------------------------------------------------------------------------

---------------------------------------------------------------------
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]



Reply via email to