Hi --
I got side-tracked a bit, but I will try to put together a code snippet.
In answer to the protocol question, the remote client uses the spi webdav
interface
Betty
- Original Message -
From: "Stefan Guggisberg" <[EMAIL PROTECTED]>
To:
Sent: Monday, July 28, 2008 5:28 AM
Subj
very useful for a business workflow where users want the ability to "revert
to last checkpoint."
and we can give them "go back to any check point" when they realize they are
going to want that. but im not telling them. ;)
On Tue, Jul 29, 2008 at 12:15 PM, Jukka Zitting <[EMAIL PROTECTED]>wrote
Hi,
On Tue, Jul 29, 2008 at 6:12 PM, Michael Harris
<[EMAIL PROTECTED]> wrote:
> It took me a minute to remember that version information is not stored in
> the workspace. So there can be a "working copy" in the workspace that is
> independent of the version copies. Users can update the working c
Jukka
It took me a minute to remember that version information is not stored in
the workspace. So there can be a "working copy" in the workspace that is
independent of the version copies. Users can update the working copy and
check in only when they are done with their updates. this is nifty
Hi,
On Tue, Jul 29, 2008 at 5:22 PM, Michael Harris
<[EMAIL PROTECTED]> wrote:
> The question is really around the save of node data without checkin. In
> this scenario, is v3 content overwritten by each save/update?
No. A save() just persists the changes in the current workspace and
doesn't mod
Fellow users,
what would happen in the following the scenaria? assume we start at v1.
do checkout, update, save, checkin
do checkout, update, save, checkin
do checkout
save
save
save
checkin
?
I would assume it would go
do checkout, update, save checkin
-- goes to v2
do checkout, update, sa
hi paco
not sure, whether i understood, what you are trying to do.
if you want to make sure that only a single user can
create/modify a given node and create new versions
of it, you should in addition to the versioning functionality
make usage of locking.
a checked-in node is prevented from bein
The problem is that when I put a document in the repository, this document
should be available for user modifications. If another user should no update
the document because he have to perform a checkout-modification-checkin
procedure.
On Tue, Jul 29, 2008 at 2:38 PM, Tobias Bocanegra
<[EMAIL PROTE
On 7/28/08, Paco Avila <[EMAIL PROTECTED]> wrote:
> In my application, a document node is uploaded to the repository and
> cheked-in. Then it is versions as 1.0 and any other user can edit it
> performing a previous check-out. The document node also is locked to
> preserve it from modifications
Paco Avila wrote:
[...] Text.escapeIllegalJcrChars(name)
that one was the right guess ;)
WebDAV bridge should perform this escaping, I think...
as i said: it's the resource-locator that does that.
see JCR-184 for the rationales why this is not implemented
by default.
angela
I lost the versionHistory node from several nodes and now isn't possible
to remove these nodes.
I would like to know how can I remove these nodes or rebuild the
versionHistory nodes.
Thanks in advance,
Tamara Coutinho
Yes, the invalid names should be escaped using ISO9075.encode(name) (or
perhaps Text.escapeIllegalJcrChars(name) or Text.escape(name) I'm not sure).
WebDAV bridge should perform this escaping, I think...
On Tue, Jul 29, 2008 at 12:14 PM, Florian Holeczek <[EMAIL PROTECTED]>wrote:
> >> There are s
ISO9075.encode(name), Text.escapeIllegalJcrChars(name) or Text.escape(name)
?
>> There are some forbidden chars in node names (:, [, ], *, \, ", |) How deal
>> WebDAV with these files? Actually server response is "500 Internal Server
>> Error" but can I escape the document names (and folder) to clean these
>> forbidden chars and get a good name? The real question is: where s
Hello gongtao,
You should limit the number of results by using setLimit and setOffset.
Then I am sure the query below will execute in several ms.
-Ard
>
> How to improve the speed,when the multi-user synchronization queries ?
> there are 1,000,000 records in the repository.
> statement:
> //[EM
Sorry for the little info. I have this node structure (okm:document is
something like nt:file)
[okm:resource] > nt:resource, mix:versionable
- okm:size (long) mandatory
- okm:author (string) mandatory
- okm:versionComment (string) copy
[okm:document] > nt:hierarchyNode, mix:referenceable, mix:loc
Yes and not. I know that the problem is related to JCR and not directly to
WebDAV but my problem is when I use JCR across WebDAV. The problem is not
the WebDAV protocol is the WebDAV-JCR bridge.
I will try yor solution. Thanks!
On Tue, Jul 29, 2008 at 11:12 AM, Angela Schreiber <[EMAIL PROTECTED]
Paco Avila wrote:
There are some forbidden chars in node names (:, [, ], *, \, ", |) How deal
WebDAV with these files? Actually server response is "500 Internal Server
Error" but can I escape the document names (and folder) to clean these
forbidden chars and get a good name? The real question is:
hi paco
I've trying to make a CHECKOUT and the server return an error: 405 Method
Not Allowed. I use "cadaver" as WebDAV client.
are you using jackrabbit 1.4?
did you make sure, that the resource is version-controlled?
with the information given, that's the first thing i
would suspect. if bot
There are some forbidden chars in node names (:, [, ], *, \, ", |) How deal
WebDAV with these files? Actually server response is "500 Internal Server
Error" but can I escape the document names (and folder) to clean these
forbidden chars and get a good name? The real question is: where should I
call
I've trying to make a CHECKOUT and the server return an error: 405 Method
Not Allowed. I use "cadaver" as WebDAV client.
On Tue, Jul 29, 2008 at 9:16 AM, Angela Schreiber <[EMAIL PROTECTED]> wrote:
> hi paco
>
> How versioning works with WebDAV?
>>
>
> do you mean in general?
> -> http://www.web
hi paco
How versioning works with WebDAV?
do you mean in general?
-> http://www.webdav.org/specs/rfc3253.html
If I upload a file to Jackrabbit
repository using WebDAV, and edit it the document version is increased?
it depends... rfc3253 defines a property called 'DAV:auto-version'
that is
22 matches
Mail list logo
