Re: JSR 170 available for Public Review
Hi Terence, this is exactly what WebDAV tries to be: A specification that is not limited to a special programming language. It's a protocol, but it can be seen it as an api (method names + (header/body)parameters ) So I'd prefer an API that brings WebDAV to the java world. Some kind of combination between Slide webdavclient and JSR-147. Regards, Daniekl Terence Kearns wrote: Davide Savazzi wrote: 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 :) just a comment on the JSR in general. It's too bad such a specification doesn't supercede a given technology (Java) as does the DOM API for instance. Then developers from other technologies (like .NET, PHP and others) could benefit in the same way all XML developers have benefited from the DOM API. You could say the same for many Java specifications I guess but this one is so inherently techno heterogeneous. It seems to me that JSR170 is like a macroscopic version of DOM -- where the repository in the case of DOM was restricted to XML packets and the XML infoset protocol. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSR 170 available for Public Review
Hi Stefan, I was trying to get the RI of JSR170 under Slide's proposal module on CVS. But the jcrri folder is empty. Is there an existing RI (other than the one available with public review) or is it yet to be started? Also is there any time frame for implementing JSR170 with slide as backend? I am particularly interested in the transactional support. Regards, Ritu -Original Message- From: Stefan Guggisberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 7:39 PM To: Slide Users Mailing List Subject: RE: JSR 170 available for Public Review 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 - 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]
RE: JSR 170 available for Public Review
Hi Stefan, hi ritu, I was trying to get the RI of JSR170 under Slide's proposal module on CVS. But the jcrri folder is empty. Is there an existing RI (other than the one available with public review) or is it yet to be started? i will commit the new ri next week. but be aware that the implementation is far from feature complete and still very instable. i will continue working on the ri in proposals/jcrri from next week on. Also is there any time frame for implementing JSR170 with slide as backend? I am particularly interested in the transactional support. the current code does not use slide. what direction slide 3.0 is heading regarding jsr 170 support has still to be discussed/decided by the community. however, the final ri will provide transactional support, someway or another. Regards, Ritu cheers stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSR 170 available for Public Review
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]
Re: JSR 170 available for Public Review
Hi Stefan, is the RI using slide as backend or is your implementation a replacement for the slide core? 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. 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. 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]
Re: JSR 170 available for Public Review
Hi,
I've posted this to [EMAIL PROTECTED], but as there is no open discussion
(mailing list/newsgroup) I post my first impressions into this archive
as well:
I'm currently having a first look at the api and like to share my very
first impressions:
First of all, it looks very mature. Congratulations to all for this
great work!
Now I'll write down some comments while looking at the api.
I assume that the api can be used locally and remote, depending on the
implementation. The standard case for sure is to talk to a repository
that is located on a different machine, so I'll look at it as a remote api.
As Geoff Clemm worked on this api, I'd be interested in how it is
related to WVCM. JSR-147 also deals with remote content repository
access so I'm interested in figuring out all of this...
* Ticket Interface
- getNodeByAbsPath(String path)
This is an ugly method name. It would be much better (might be a matter
of taste, but I don't like shortcuts) to have a method like
getNode(Path path)
So the Path-class could deal with relative and absolute paths and have
some nice helper methods. Think of something like this
interface Path {
boolean isRelative();
boolean isAbsolute();
Path append(Path path);
boolean isDescendant(Path path);
boolean isAncestor(Path path);
boolean isChild(Path path);
...
}
The same for getNode(UURI uuri)...
- What about this revert/save methods?
In the java world I'd expect that a content repository is accessed using
JCA. Any datasource is configured in the J2EE-specific way.
Think of the following scenario:
An application is using different datasources (oracle rdbms, content
repository via jsr-170). So the user is starting a transaction and doing
some modifications to the data. The transaction manager cares if the
data should be rolled back or commited.
Depending on the transactions isolation level the user can query the
repository or database via it's query languages (sql, xpath or JCRQL)
and gets the result including the changes he made.
So why should the user care of any save/revert methods? Is search only
possible on the repository data after save()?
I'll have a closer look on the api soon and I can post some more if
comments are appreciated.
Regards,
Daniel Florey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSR 170 available for Public Review
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 - 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]
Re: JSR 170 available for Public Review
Stefan Guggisberg wrote: 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 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. 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]
