What is in the future for Slide?
Oliver Zeigermann wrote:
Not impolite at all, I understand your reservation. While I am the original author of WCK, I am currently not actively involved in neither developing Slide further nor in any release roadmaps. Sorry...
Still when developing your own store you can still have a look at WCK for inspiration as it is a "normal" store implementation as well.
E.g. have a look at
org.apache.slide.simple.store.WebdavStoreAdapter
which extends
AbstractXAServiceBase
and implements
Service, ContentStore, NodeStore, LockStore, RevisionDescriptorStore and RevisionDescriptorsStore
Oliver
On 5/4/05, Derek Richardson <[EMAIL PROTECTED]> wrote:
Yes, I think I would prefer to use WCK, since it's targeted for this purpose (I haven't looked at it yet). However, I am concerned about using it in production without a "final" release. Is there a timeframe for a release that would include WCK?
Please excuse the impolite question, but it's critical to my ability to use. ;)
Thanks.
-----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 3:21 PM To: Slide Users Mailing List Subject: Re: NEWBIE: Full Custom Store
Have you considered using WCK instead?
Oliver
On 5/4/05, Derek Richardson <[EMAIL PROTECTED]> wrote:
Hi. I'm new to Slide and am interested in using it to provide webDAV implemented on top of another CMS. I found the
IntroFullCustomStore page
on the wiki
(http://wiki.apache.org/jakarta-slide/IntroFullCustomStore),
which details what I need to do. I am confused by the following paragraph:
"Anyway, looking at your store this way you have to specify six interfaces - and an optional one - for a complete store definition. Additionally, you will need to implement an XAResource to
let your store
participate in a distributed transaction. This interface is
specified by
the JTA and is needed by Slide's internal transaction manager which also is more or less compliant to the JTA. Slide also requires the implementation of org.apache.slide.common.Service. I'd recommend to start from AbstractServiceBase as it sensibly implements many of the methods in Service interface."
The six interfaces are later listed as:
1: RevisionDescriptorStore 2: ContentStore 3: RevisionDescriptorsStore 4: NodeStore 5: SecurityStore 6: LockStore
According to the above paragraph, I also need to implement
Service and
XAResource, which makes for eight types to implement and I'm unsure about what is supposed to the the "optional" one that I apparently *must* implement, as well. Will someone clarify this for me?
Thanks.
---------------------------------------------------------------------
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
