Re: Unique ID for a document in the slide repository ?
Using an event listener you could set a GUID on each resource as it is created, or if you have a custom store you could expose the unique ID as a property. Of course, the only way to *retrieve* an object based on the value of this property is through a search, so I don't know how useful it would be. -James On Thu, 2004-12-09 at 02:42 +0200, Roman D wrote: > I was looking for something similar, but since it's not a part of Webdav > protocol, it'll never be in Slide. > > I take URI and find database object by splitting it, then you can find > your unique ID from DB object. > > > Nick Longinow wrote: > > Hi > > > > > > > > It seems that the uri for a document (resource) in the slide repository is > > the only unique identifier. This poses problems for applications which > > record the id elsewhere, like in a database, and then have to deal with a > > rename of a node upstream in the document's parent tree. Is there any other > > id, such as a guid, for identifiying the resource ? > > > > Nick > > > > > > > > - > 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: Cluster cache
The way it's *supposed* to work is you only get notifications for changes that occur within the collection you specify. I can't recall actually testing that case, though. Again, I think this part relies on the notification mechanism to determine which events are relevant, so the documentation Daniel mentioned might have clues. -James On Wed, 2004-12-08 at 10:24 -0800, Warwick Burrows wrote: > This is exactly what I needed James. Thanks! > > > They should be asynchronous. Daniel Florey wrote the > > notification mechanism, so he can confirm, but I'm pretty > > sure on this. > > Daniel, can you confirm that notifications are asynchronous? Or is there a > write-up on the notifications that I can look at? > > And I have another question on the cluster cache :-) There is a "base-uri" > parameter that is specified in the configuration. If this is set to "/files" > will it pick up all changes to objects under /files? For example when a file > is checked out/in with a new revision will it also notify other slide > servers of /history path updates that stem from the change even though > /history isn't specifically configured as the base-uri? > > Thanks, > Warwick > > > > -Original Message- > > From: James Mason [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, December 07, 2004 8:40 PM > > To: Warwick Burrows; Slide Users Mailing List > > Subject: Re: Cluster cache > > > > > > On Tue, 2004-12-07 at 18:10 -0800, Warwick Burrows wrote: > > > Hi James, > > > > > > I was hoping you could answer some questions about the > > cluster cache > > > design. We would like to go into production with Slide but doing so > > > requires the cluster cache implementation -- or no caching at all > > > which is not even an option :-) We need to know the cluster cache > > > mechanics so we can cater for them. > > > > > > - Are the updates (notifications) between servers performed > > > synchronously or asynchronously? > > > > They should be asynchronous. Daniel Florey wrote the > > notification mechanism, so he can confirm, but I'm pretty > > sure on this. When a resource is modified the server sends > > notifications to all subscribers that there are events > > waiting for them. The subscribers (other servers) then POLL > > the server and get a list of changed resources. Each > > subscriber then removes the resource in the list from their cache. > > > > > - If an update to a server fails will it be retried? > > > > It depends on where the failure is. If a subscriber is unable > > to POLL a server, it will retry. In fact, each subscriber > > periodically POLLs the server just to be sure it hasn't > > missed any notifications. The POLL frequency should be configurable. > > > > > > > > Any other design points I should be aware of? > > > > Not that I can think of. > > > > > > > > Incidentally I had mentioned that locks could be an issue with the > > > cache design in that two lock requests coming in at the > > same time may > > > both return with the lock. It isn't an issue for us though > > as locking > > > is controlled by our DAV applications and the lock information they > > > share is stored in a DB. Only one app is guaranteed to get the lock > > > and so create a Slide lock. One way to mitigate this > > problem for other > > > clients may be to allow for the "lockstore" store to be > > specifically > > > configured so that only lock related metadata isn't cached. > > > > ExtendedStore has five (I think) separate caches. You can set > > the size of each cache by setting parameters on the store. > > One of the caches is for locks. Take a look at the source for > > ExtendedStore, since I'm not sure where, if anywhere, the > > parameters are documented. > > > > -James > > > > > > > > Thanks, > > > Warwick > > > > > > > > > > - > 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: Unique ID for a document in the slide repository ?
I was looking for something similar, but since it's not a part of Webdav protocol, it'll never be in Slide. I take URI and find database object by splitting it, then you can find your unique ID from DB object. Nick Longinow wrote: Hi It seems that the uri for a document (resource) in the slide repository is the only unique identifier. This poses problems for applications which record the id elsewhere, like in a database, and then have to deal with a rename of a node upstream in the document's parent tree. Is there any other id, such as a guid, for identifiying the resource ? Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WCK Transaction error during commit
Hi John, I made a submission to the HEAD to fix external transaction support last night. If you are using client-side transactions then this may have introduced the problem but it is working in the Slide 2.1 release currently. To be using client-side transactions you would be calling the WebdavResource startTransaction(), abortTransaction() and commitTransaction() methods to wrap your requests to the Slide server. If you're using client-side transactions then I've made a change to four files that you will need to pick up for the fix. They are AbstractWebdavMethod.java, EventCollectionFilter.java, the server UnlockMethod.java and client WevdavResource.java. Whenever you start a transaction with startTransaction() you should use the same path to abort or commit that transaction otherwise the webdav client can lose track of the transaction lock. I've been using the "/slide" path for transactions. If you're not using client side transactions then this is probably not the issue as the conditions met by isEndOfTransactionRequest() are only met by an external transaction and specifically by an UnlockMethod that contains a commit or abort command. Warwick > -Original Message- > From: John Rousseau [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 08, 2004 1:17 PM > To: Slide Users Mailing List > Subject: WCK Transaction error during commit > > > I've been working with WCK for about a week now and today I started > seeing these exceptions. I backed out all recent > configuration changes > and updated from HEAD, but I'm still seeing these. > > The exception is caused by commons/transaction's > AbstractXAResource not > being able to find the current transaction, but I have no idea why. > > Ideas? > > Thanks > -John > > > 08 Dec 2004 13:24:43 - > org.apache.slide.transaction.SlideTransaction - WARNING - > Commit failure: Resource manager > [EMAIL PROTECTED] Error code > XAER_NOTA in Transaction 2 xid [EMAIL PROTECTED]@a0d37f in thread > PoolThread-14 javax.transaction.xa.XAException > at > org.apache.commons.transaction.util.xa.AbstractXAResource.comm > it(AbstractXAResource.java:69) > at > org.apache.slide.transaction.SlideTransaction.commit(SlideTran > saction.java:300) > at > org.apache.slide.transaction.SlideTransactionManager.commit(Sl > ideTransactionManager.java:186) > at > org.apache.slide.common.NamespaceAccessTokenImpl.commit(Namesp > aceAccessTokenImpl.java:423) > at > org.apache.slide.webdav.method.AbstractWebdavMethod.run(Abstra > ctWebdavMethod.java:463) > at > org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:151) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:354) > at > org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter > (WebApplicationHandler.java:342) > at > org.apache.slide.webdav.filter.LogFilter.doFilter(LogFilter.java:141) > at > org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter > (WebApplicationHandler.java:334) > at > com.ris.manager.gateway.http.IPAddressRestriction.doFilter(IPA > ddressRestriction.java:248) > at > org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter > (WebApplicationHandler.java:334) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebAp > plicationHandler.java:286) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler > .java:567) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1808) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebAppl > icationContext.java:525) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1758) > at org.mortbay.http.HttpServer.service(HttpServer.java:879) > at > org.mortbay.http.HttpConnection.service(HttpConnection.java:790) > at > org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952) > at > org.mortbay.http.HttpConnection.handle(HttpConnection.java:807) > at > org.mortbay.http.SocketListener.handleConnection(SocketListene > r.java:197) > at > org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) > at > org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501) > > > - > 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]
WCK Transaction error during commit
I've been working with WCK for about a week now and today I started seeing these exceptions. I backed out all recent configuration changes and updated from HEAD, but I'm still seeing these. The exception is caused by commons/transaction's AbstractXAResource not being able to find the current transaction, but I have no idea why. Ideas? Thanks -John 08 Dec 2004 13:24:43 - org.apache.slide.transaction.SlideTransaction - WARNING - Commit failure: Resource manager [EMAIL PROTECTED] Error code XAER_NOTA in Transaction 2 xid [EMAIL PROTECTED]@a0d37f in thread PoolThread-14 javax.transaction.xa.XAException at org.apache.commons.transaction.util.xa.AbstractXAResource.commit(AbstractXAResource.java:69) at org.apache.slide.transaction.SlideTransaction.commit(SlideTransaction.java:300) at org.apache.slide.transaction.SlideTransactionManager.commit(SlideTransactionManager.java:186) at org.apache.slide.common.NamespaceAccessTokenImpl.commit(NamespaceAccessTokenImpl.java:423) at org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:463) at org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:151) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:354) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342) at org.apache.slide.webdav.filter.LogFilter.doFilter(LogFilter.java:141) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334) at com.ris.manager.gateway.http.IPAddressRestriction.doFilter(IPAddressRestriction.java:248) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1808) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1758) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:790) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Cluster cache
You can have a look at the package.html in the event package (javadocs). Also have a look at google: notification webdav (ms exchange site). I've implemented the notifications in the same way that it is done in Ms Exchange (with some extensions regarding the depth-header). Cheers, Daniel > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Im Auftrag von Warwick Burrows > Gesendet: Mittwoch, 8. Dezember 2004 19:24 > An: 'Slide Users Mailing List' > Betreff: RE: Cluster cache > > > This is exactly what I needed James. Thanks! > > > They should be asynchronous. Daniel Florey wrote the > > notification mechanism, so he can confirm, but I'm pretty > > sure on this. > > Daniel, can you confirm that notifications are asynchronous? Or is there a > write-up on the notifications that I can look at? > > And I have another question on the cluster cache :-) There is a "base-uri" > parameter that is specified in the configuration. If this is set to > "/files" > will it pick up all changes to objects under /files? For example when a > file > is checked out/in with a new revision will it also notify other slide > servers of /history path updates that stem from the change even though > /history isn't specifically configured as the base-uri? > > Thanks, > Warwick > > > > -Original Message- > > From: James Mason [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, December 07, 2004 8:40 PM > > To: Warwick Burrows; Slide Users Mailing List > > Subject: Re: Cluster cache > > > > > > On Tue, 2004-12-07 at 18:10 -0800, Warwick Burrows wrote: > > > Hi James, > > > > > > I was hoping you could answer some questions about the > > cluster cache > > > design. We would like to go into production with Slide but doing so > > > requires the cluster cache implementation -- or no caching at all > > > which is not even an option :-) We need to know the cluster cache > > > mechanics so we can cater for them. > > > > > > - Are the updates (notifications) between servers performed > > > synchronously or asynchronously? > > > > They should be asynchronous. Daniel Florey wrote the > > notification mechanism, so he can confirm, but I'm pretty > > sure on this. When a resource is modified the server sends > > notifications to all subscribers that there are events > > waiting for them. The subscribers (other servers) then POLL > > the server and get a list of changed resources. Each > > subscriber then removes the resource in the list from their cache. > > > > > - If an update to a server fails will it be retried? > > > > It depends on where the failure is. If a subscriber is unable > > to POLL a server, it will retry. In fact, each subscriber > > periodically POLLs the server just to be sure it hasn't > > missed any notifications. The POLL frequency should be configurable. > > > > > > > > Any other design points I should be aware of? > > > > Not that I can think of. > > > > > > > > Incidentally I had mentioned that locks could be an issue with the > > > cache design in that two lock requests coming in at the > > same time may > > > both return with the lock. It isn't an issue for us though > > as locking > > > is controlled by our DAV applications and the lock information they > > > share is stored in a DB. Only one app is guaranteed to get the lock > > > and so create a Slide lock. One way to mitigate this > > problem for other > > > clients may be to allow for the "lockstore" store to be > > specifically > > > configured so that only lock related metadata isn't cached. > > > > ExtendedStore has five (I think) separate caches. You can set > > the size of each cache by setting parameters on the store. > > One of the caches is for locks. Take a look at the source for > > ExtendedStore, since I'm not sure where, if anywhere, the > > parameters are documented. > > > > -James > > > > > > > > Thanks, > > > Warwick > > > > > > > > > > - > 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: Cluster cache
This is exactly what I needed James. Thanks! > They should be asynchronous. Daniel Florey wrote the > notification mechanism, so he can confirm, but I'm pretty > sure on this. Daniel, can you confirm that notifications are asynchronous? Or is there a write-up on the notifications that I can look at? And I have another question on the cluster cache :-) There is a "base-uri" parameter that is specified in the configuration. If this is set to "/files" will it pick up all changes to objects under /files? For example when a file is checked out/in with a new revision will it also notify other slide servers of /history path updates that stem from the change even though /history isn't specifically configured as the base-uri? Thanks, Warwick > -Original Message- > From: James Mason [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 07, 2004 8:40 PM > To: Warwick Burrows; Slide Users Mailing List > Subject: Re: Cluster cache > > > On Tue, 2004-12-07 at 18:10 -0800, Warwick Burrows wrote: > > Hi James, > > > > I was hoping you could answer some questions about the > cluster cache > > design. We would like to go into production with Slide but doing so > > requires the cluster cache implementation -- or no caching at all > > which is not even an option :-) We need to know the cluster cache > > mechanics so we can cater for them. > > > > - Are the updates (notifications) between servers performed > > synchronously or asynchronously? > > They should be asynchronous. Daniel Florey wrote the > notification mechanism, so he can confirm, but I'm pretty > sure on this. When a resource is modified the server sends > notifications to all subscribers that there are events > waiting for them. The subscribers (other servers) then POLL > the server and get a list of changed resources. Each > subscriber then removes the resource in the list from their cache. > > > - If an update to a server fails will it be retried? > > It depends on where the failure is. If a subscriber is unable > to POLL a server, it will retry. In fact, each subscriber > periodically POLLs the server just to be sure it hasn't > missed any notifications. The POLL frequency should be configurable. > > > > > Any other design points I should be aware of? > > Not that I can think of. > > > > > Incidentally I had mentioned that locks could be an issue with the > > cache design in that two lock requests coming in at the > same time may > > both return with the lock. It isn't an issue for us though > as locking > > is controlled by our DAV applications and the lock information they > > share is stored in a DB. Only one app is guaranteed to get the lock > > and so create a Slide lock. One way to mitigate this > problem for other > > clients may be to allow for the "lockstore" store to be > specifically > > configured so that only lock related metadata isn't cached. > > ExtendedStore has five (I think) separate caches. You can set > the size of each cache by setting parameters on the store. > One of the caches is for locks. Take a look at the source for > ExtendedStore, since I'm not sure where, if anywhere, the > parameters are documented. > > -James > > > > > Thanks, > > Warwick > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Choosing between multiple namespace and multiple stores
I asked the same question a little while ago. It sounds like the advantages of using one configuration over the other are not entirely clear. Multiple stores are much easier to configure than multiple namespaces, so I would probably go with this configuration. I suppose that using multiple namespaces might give you more control if you want these namespaces to behave very differently (e.g. with regards to versioning, permissions, etc.), but then again I don't really know. -Mirko On Wed, 2004-12-08 at 00:00, Ritu Kedia wrote: > Could someone please point out the pros and cons of using multiple > namespaces vs multiple stores. I have a requirement of configuring multiple > slide stores in a single App Instance. Each store will be used by a > different set of people. > I would also like to know if there are known issues with either > configuration and which one would be more performant and stable. > > Thanks, > Ritu > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: history-collection-hack bug
Well from what I can see, there should be no problem with the combination!
The only thing is this getHistoryPathHandler function! However to resolve
the history path I need some information that is not available in the class
by default, but as I said I am not very familiar with this part of the code.
/jacob
- Original Message -
From: "Oliver Zeigermann" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, December 08, 2004 3:47 PM
Subject: Re: history-collection-hack bug
???
Maybe the problem is that the history folder structures with the hack
turned on / off are incompatible?
Oliver
On Wed, 8 Dec 2004 15:41:02 +0100, Jacob Lund <[EMAIL PROTECTED]> wrote:
OK - I think I found the origin of the problem.
In the HistoryPathHandler class there are 2 getHistoryPathHandler
functions,
but only one of them are handling the situation where the history path
has a
parameter in it.
I don't know this part of the code very well, so I don't have a solution
yet.
/jacob
- Original Message -
From: "Jacob Lund" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, December 07, 2004 3:42 PM
Subject: Re: history-collection-hack bug
>I am looking into it now - i just found out!
>
> It does not throw an exception! I will report back as soon as I have
> something.
>
> /jacob
>
> - Original Message -
> From: "Oliver Zeigermann" <[EMAIL PROTECTED]>
> To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
> Sent: Tuesday, December 07, 2004 3:35 PM
> Subject: Re: history-collection-hack bug
>
>
>> Any idea what the problem with the hack is?
>>
>> Oliver
>>
>>
>> On Tue, 7 Dec 2004 12:33:16 +0100, Jacob Lund <[EMAIL PROTECTED]>
>> wrote:
>>> Hi all,
>>>
>>> When slide is configured to split the history collection into
>>> seperate
>>> stores /history/${store},
>>> then
>>> the history-collection-hack breaks the versioning part of slide.
>>>
>>> I have attached an example domain.xml file. When
>>> history-collection-hack
>>> is
>>> set to false it works fine.
>>>
>>> I tested this with 2.1rc1.
>>>
>>> /jacob
>>>
>>>
>>> -
>>> 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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: history-collection-hack bug
???
Maybe the problem is that the history folder structures with the hack
turned on / off are incompatible?
Oliver
On Wed, 8 Dec 2004 15:41:02 +0100, Jacob Lund <[EMAIL PROTECTED]> wrote:
> OK - I think I found the origin of the problem.
>
> In the HistoryPathHandler class there are 2 getHistoryPathHandler functions,
> but only one of them are handling the situation where the history path has a
> parameter in it.
>
> I don't know this part of the code very well, so I don't have a solution
> yet.
>
> /jacob
>
>
>
>
> - Original Message -
> From: "Jacob Lund" <[EMAIL PROTECTED]>
> To: "Slide Users Mailing List" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, December 07, 2004 3:42 PM
> Subject: Re: history-collection-hack bug
>
> >I am looking into it now - i just found out!
> >
> > It does not throw an exception! I will report back as soon as I have
> > something.
> >
> > /jacob
> >
> > - Original Message -
> > From: "Oliver Zeigermann" <[EMAIL PROTECTED]>
> > To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
> > Sent: Tuesday, December 07, 2004 3:35 PM
> > Subject: Re: history-collection-hack bug
> >
> >
> >> Any idea what the problem with the hack is?
> >>
> >> Oliver
> >>
> >>
> >> On Tue, 7 Dec 2004 12:33:16 +0100, Jacob Lund <[EMAIL PROTECTED]> wrote:
> >>> Hi all,
> >>>
> >>> When slide is configured to split the history collection into seperate
> >>> stores /history/${store},
> >>> then
> >>> the history-collection-hack breaks the versioning part of slide.
> >>>
> >>> I have attached an example domain.xml file. When history-collection-hack
> >>> is
> >>> set to false it works fine.
> >>>
> >>> I tested this with 2.1rc1.
> >>>
> >>> /jacob
> >>>
> >>>
> >>> -
> >>> 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: history-collection-hack bug
OK - I think I found the origin of the problem.
In the HistoryPathHandler class there are 2 getHistoryPathHandler functions,
but only one of them are handling the situation where the history path has a
parameter in it.
I don't know this part of the code very well, so I don't have a solution
yet.
/jacob
- Original Message -
From: "Jacob Lund" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, December 07, 2004 3:42 PM
Subject: Re: history-collection-hack bug
I am looking into it now - i just found out!
It does not throw an exception! I will report back as soon as I have
something.
/jacob
- Original Message -
From: "Oliver Zeigermann" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 07, 2004 3:35 PM
Subject: Re: history-collection-hack bug
Any idea what the problem with the hack is?
Oliver
On Tue, 7 Dec 2004 12:33:16 +0100, Jacob Lund <[EMAIL PROTECTED]> wrote:
Hi all,
When slide is configured to split the history collection into seperate
stores /history/${store},
then
the history-collection-hack breaks the versioning part of slide.
I have attached an example domain.xml file. When history-collection-hack
is
set to false it works fine.
I tested this with 2.1rc1.
/jacob
-
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: Idea on final release of Slide 2.1
Agreed. I'd be all +1 even if more minor issues arise with rc1. I am repeating myself, but compare 2.1rc1 to 2.0 and you will know why... Oliver On Wed, 08 Dec 2004 00:13:45 -0800, James Mason <[EMAIL PROTECTED]> wrote: > Hopefully before the end of the year. It's looking pretty stable, and > most of us are getting anxious for another release. > > -James > > > > On Tue, 2004-12-07 at 14:44 -0600, Chris O'Connell wrote: > > Anyone have an idea of when the final release of Slide 2.1 will be > > available? > > > > Regards, > > Chris > > > > - > > 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: WebDav LOCK and MOVE question
Hello, Thx for your feedback Warwick. Unfortunately I also have to ensure that no client already starts to download the file while the upload is in progress. Moreover the clients are small mobile devices and have no logic for 423 error codes. Therefore I have to upload the data to a temporary file and then move the temporary file to the destination. Thx, Bernd > -Original Message- > From: Warwick Burrows [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 07, 2004 8:55 PM > To: 'Slide Users Mailing List' > Subject: RE: WebDav LOCK and MOVE question > > Bernd, > > Slide's WebDAV client creates a lock-null resource when you lock a file > that > doesn't exist and that you want to create. This is how the WebDAV standard > deals with two uploads of the same new file at the same time. When the > second server tries to lock the resource they will be denied with the 423 > error code. So you don't need a temp file (I don't think) as the WebDAV > server creates it for you. > > So to do what you want and assuming that all of your clients that are > doing > uploads simultaneously will be your DAV clients then you need to: > > 0) Check whether the file already exists on the file server. > If yes => done > 1) Call webdav client lockMethod on target file (creates lock-null > resource) > 2) Call webdav client putMethod to upload bytes to the lock-null > file. > 4) Unlock the lock with webdav client unlockMethod on target file. > > Try this approach and you should not see the 423 error you're seeing now - > - > at least if you're using the Slide 2.1 WebDAV client which I am using and > which passes the lock to the server in the request as it is supposed to. > > Warwick > > > > > -Original Message- > > From: Bernd Kühl [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, December 07, 2004 9:34 AM > > To: Slide Users Mailing List; [EMAIL PROTECTED] > > Subject: RE: WebDav LOCK and MOVE question > > > > > > Hello, > > > > Yes I have a problem with the move. Please find attached a > > simple test program. The output of the program is > > > > Empty put temp file status is 201, result is true > > Put temp file status is 201, result is true > > lock temp file status is 200, result is true > > Put temp file status is 423, result is false > > Move status is 201, result is true > > unlock status is 204, result is true > > > > As you see I get a 423 error status code for the move. Apache logged: > > > > [Tue Dec 07 16:30:42 2004] [error] [client 172.16.8.1] This > > resource is locked and an "If:" header was not supplied to > > allow access to the resource. [423, #0] > > > > I do not understand why no (or the wrong) If: is supplied to > > the move request. > > > > Who can help me? > > > > Thx, > > > > Bernd > > > > > > > -Original Message- > > > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, December 07, 2004 4:18 PM > > > To: Slide Users Mailing List > > > Subject: Re: WebDav LOCK and MOVE question > > > > > > So, you still could has a problem while moving the temporary file. > > > > > > Bottom line: You try to reimplement transactional features > > modav does > > > not seem to have. Maybe then it is not the right choice in > > the first > > > place. > > > > > > Oliver > > > > > > > > > On Tue, 7 Dec 2004 16:06:49 +0100, Bernd Kühl > > > <[EMAIL PROTECTED]> > > > wrote: > > > > Hello, > > > > > > > > It is "Apache/2.0.44 (Unix) DAV/2 mod_webapp/1.2.0-dev". > > > > > > > > Just uploading the file is not good enough since then different > > > > server > > > machines can do the upload in parallel. Moreover a client > > machine can > > > fetch the file while a [slow] server machine is currently doing the > > > upload. This leads into a corrupted file. > > > > > > > > Thx, > > > > > > > > Bernd > > > > > > > > > > > > > > > > > -Original Message- > > > > > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > > > > > Sent: Tuesday, December 07, 2004 3:47 PM > > > > > To: Slide Users Mailing List > > > > > Subject: Re: WebDav LOCK and MOVE question > > > > > > > > > > What is the WebDAV server you are programming to? Slide? If so, > > > > > just upload the file. > > > > > > > > > > Oliver > > > > > > > > > > On Tue, 7 Dec 2004 15:11:42 +0100, Bernd Kühl > > > <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > Hello, > > > > > > > > > > > > I want to upload a file to a web server. Several > > machines maybe > > > > > > try > > > in > > > > > parallel to upload the same file. Therefore locking is > > needed to > > > > > allow only one upload. Moreover I have to ensure that no other > > > > > machine > > > downloads > > > > > the file before the complete upload is done. So the algorithm I > > > > > have > > > in > > > > > mind goes like this: > > > > > > > > > > > > 0) Check whether the file already exists on the file > > server. If > > > > > > yes > > > => > > > > > done > > > > > > 1) Lock non existing temporary file. > > > > > > 2) Upload the by
Re: Idea on final release of Slide 2.1
Hopefully before the end of the year. It's looking pretty stable, and most of us are getting anxious for another release. -James On Tue, 2004-12-07 at 14:44 -0600, Chris O'Connell wrote: > Anyone have an idea of when the final release of Slide 2.1 will be available? > > Regards, > Chris > > - > 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]
Choosing between multiple namespace and multiple stores
Could someone please point out the pros and cons of using multiple namespaces vs multiple stores. I have a requirement of configuring multiple slide stores in a single App Instance. Each store will be used by a different set of people. I would also like to know if there are known issues with either configuration and which one would be more performant and stable. Thanks, Ritu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide 2.1rc1 thrid party libraries info
Most of the jars have the version number as part of the file name. For those that don't, you can check the MANIFEST files, but most don't have version info. Your best bet will probably be the dates on the CVS commit logs. That will give you a rough idea of when the library was created. At worst this will tell you the latest possible version number. -James On Tue, 2004-12-07 at 17:58 -0800, Gao Jun wrote: > Hi, > > Where could I find detailed version info about all the third party libraries > which slide 2.1rc1 is depending on? Like jdom, xerces, etc. We need to > compare those libraries' version info with > those we already have in our application to see whether we should replace > them. Thanks a lot. > > regards, > > Jun > > > - > Do you Yahoo!? > Yahoo! Mail - 250MB free storage. Do more. Manage less. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
