Stefan Guggisberg wrote:
I like this aproach, but is this not more or less what WVCM is dealing with? To be honest: I still don't see, why there are two jsr's dealing with a repository api. The focus of jsr-147 seems to be more on the versioning (deltaV) stuff, but what we need is one java api for repository access including all features like acl, search, versioning, locking, versioning and all of this.Hi Stefan,
is the RI using slide as backend or is your implementation a replacement
for the slide core?
the current implementation of the ri has no dependencies on slide. it is a proposal only. what future direction the implementation will take is open.
As we spent some time on improving the slide backend (tx filestore,
improved db-stores) it would be nice to have this features available by
using the jsr170 api.
i totally agree.
What about the webdav layer? Is your plan that it will be using the
jsr170-RI in future. If so please remind that we are working hardly to
make slide more MS exchange compatible by adding notification, search
and transaction-support via webav.
remy sketched a possible architecture in his initial proposal:
<quote>
- WebDAV powered JSR 170 client API
To have the same api on client and server side is a big plus, so I'll vote for jsr-170 as this seems to include more of this features.
The hard task is to handle all of the webdav specific requirements on api level so that content in the repository can be accessed and modified using the api layer or the webdav layer with same features and consistent data. At the moment you can't do the versioning stuff on slide api layer, because this changes don't get reflected properly on deltaV level.
So I hope that jsr-170 fulfills all requirement that deltav and acl and the other protocols needs to get this running.
Another big point is that it should be possible to access existing repositories with the java api. So if we take the most relevant ones as filesystem, cvs, subversion and other repositories it should be possible to access them with the jsr-170 api. So that if you checkin something in cvs, a new revision in jsr-170-based repository is also available.
Regards,
Daniel
- WebDAV server layer, using JSR 170 API - Slide core, providing a JSR 170 API </quote>
imo, such an architecture would make perfectly sense. but of course, the community has to come up with a strategy/decision regarding a future version of slide & jsr 170.
cheers stefan
Best regards, Daniel
Stefan Guggisberg wrote:
hi davide there will be an implementation of the jcr api located in the slide cvs under /proposals/jcrri, available soon. this implementation will represent work in progress.
fyi: i'am working on this proposal, on and off, since feb 2003. we had to remove the code from the slide cvs a while ago for legal reasons. but since the jsr 170 spec is now in public review these issues do not exist anymore.
for a possible architecture, see remy's initial post: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05538.html
cheers stefan
-----Original Message----- From: Davide Savazzi [mailto:[EMAIL PROTECTED] Sent: Dienstag, 18. Mai 2004 10:07 To: 'Slide Users Mailing List' Subject: JSR 170 available for Public Review
http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :)
-- Davide Savazzi
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
