I have slide 2.1 working with utf8. But you should notice that windows 2000
with office 97 and DAVExplorer does not support utf8.
Have a look at: http://greenbytes.de/tech/webdav/webfolder-client-list.html
/jacob
- Original Message -
From: Alexandre Clavaud [EMAIL PROTECTED]
To:
Hi guys,
We found that when PROPPATCH is executed on a versionable resource a new
version (new file or VERSION_CONTENT record in case of RDBMS) of content
is produced too. This leads to inacceptable cloning of content which
leads to storage size growth. When we plan to store thousands or even
Then, rather than using utf8, should I use ISO8859-1 ?
I have slide 2.1 working with utf8. But you should notice that windows
2000
with office 97 and DAVExplorer does not support utf8.
Have a look at:
http://greenbytes.de/tech/webdav/webfolder-client-list.html
/jacob
-
Hello...
I'm a new slide user, now i'm trying to use slide and i have a few
question about it.
- Could you please tell me how to set up slide as a webdav server an how
to integrate it with Tomcat, i use Tomcat 5.0.28 and slide 2.0 ?
- Is it possible to have a manipulation namespaces, locking
Hi,
Is it possible to have a case sensitive DASL search with these arguments
D:contains/D:contains
and
SLIDE:propcontains xmlns:SLIDE=http://jakarta.apache.org/slide/;
D:propD:displayname//D:prop
D:literal/D:literal
/SLIDE:propcontains
I've tried with a caseless attribute
Hooow shit!
Tried here. Indeed slide mess with the accents when sending it's result to the
client. I created a file with accents. Platform encoding is utf-8, slide
encoding is utf-8, client is the kde webdav protocol working nicely with
accent on other webdav implementations. However, result of
Thanks, that will be great.
I have to projects:
1. For a customer, using Slide as Document Management repository, accessing
from WebFolder and from Java applications.
2. For Compiere, an Open Source ERP, using Slide as Document Management
repository full integrated in the application, with
I have tested slide 2.1 and utf8 with filestore and SQLServer store - both
are working fine.
Make sure that slide has been set to utf8 in slide.priperties file, that the
connector in server.xml is set to utf8, and the store is using utf8.
The only bug I have found in slide 2.1 with resprct to
Submitted a detailed bug report of problem. I hope the slide devels will fix
this fast!
http://issues.apache.org/bugzilla/show_bug.cgi?id=34679
Le Vendredi 29 Avril 2005 12:55, Alexandre Clavaud a écrit :
Thanks, that will be great.
I have to projects:
1. For a customer, using Slide as
Will try something similar with slide 2.1, thanks for suggestion.
Le Vendredi 29 Avril 2005 16:55, Alexandre Clavaud a écrit :
I managed to patch it (working with Slide-cvs-head-2.2pre1) :
1. Use org.apache.slide.urlEncoding=ISO8859-1 in slide.properties
2. In
The ideal here, of course, would be for versioning to store deltas. If a
property changes, record the change in the property alone, etc. If the
content is text and the content changes, store a diff, not a new copy (much
like CVS). If the content is binary, then store a binary delta. There
Denis Zvonov wrote:
Another issue with Oracle store implementation. Revoking of privileges
from resources has error in SQL statement and does not work. We use Slide 2.1
Yes, there was a missing right parenthesis in the SQL since one of the Slide
developers (presumable without the possibility to
12 matches
Mail list logo
