Re: Slide Tomcat Sessions - Closing them
Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had). I shall now recode based on your advice though - thank you for your help. Cheers Luke. - Quoting Ingo Brunberg [EMAIL PROTECTED]: Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide Tomcat Sessions - Closing them
Hmm, either I misunderstood what you meant, or it doesn't quite fix things the way I expected. I now only construct one webdav resource in my code, however, after running just a few simple getMethods, propFindMethods and reportMethods 5 sessions are created when I expected only one to be created. Any further suggestions? Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had). I shall now recode based on your advice though - thank you for your help. Cheers Luke. - Quoting Ingo Brunberg [EMAIL PROTECTED]: Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. - 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: Slide Tomcat Sessions - Closing them
After a bit more investigation, it seems that constructing a new HttpURL or using the getHttpURL() method of WebdavResource also creates a new session. Should it be doing this? Is there a way to avoid it doing so? There are some cases where I can see no way of doing what I want without constructing a new WebdavResource or a HttpURL. Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hmm, either I misunderstood what you meant, or it doesn't quite fix things the way I expected. I now only construct one webdav resource in my code, however, after running just a few simple getMethods, propFindMethods and reportMethods 5 sessions are created when I expected only one to be created. Any further suggestions? Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had). I shall now recode based on your advice though - thank you for your help. Cheers Luke. - Quoting Ingo Brunberg [EMAIL PROTECTED]: Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. - 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: Slide Tomcat Sessions - Closing them
This is indeed worth investigating. Calling getHttpURL() should really not create a new session. Maybe you can post a code snippet? Ingo After a bit more investigation, it seems that constructing a new HttpURL or using the getHttpURL() method of WebdavResource also creates a new session. Should it be doing this? Is there a way to avoid it doing so? There are some cases where I can see no way of doing what I want without constructing a new WebdavResource or a HttpURL. Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hmm, either I misunderstood what you meant, or it doesn't quite fix things the way I expected. I now only construct one webdav resource in my code, however, after running just a few simple getMethods, propFindMethods and reportMethods 5 sessions are created when I expected only one to be created. Any further suggestions? Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had). I shall now recode based on your advice though - thank you for your help. Cheers Luke. - Quoting Ingo Brunberg [EMAIL PROTECTED]: Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. - 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: Slide Tomcat Sessions - Closing them
Hi Luke, I recently dug into the WebdavResource while trying to solve my own problems. I ended up making my own method calls using HttpClient and some of the Webdav methods. Doing it this way, I was able to reuse the same instance of the HttpClient for all of my method calls and only 1 session is created. Ryan- -Original Message- From: luke noel-storr [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 11:51 AM To: Slide Users Mailing List Subject: Re: Slide Tomcat Sessions - Closing them Hmm, either I misunderstood what you meant, or it doesn't quite fix things the way I expected. I now only construct one webdav resource in my code, however, after running just a few simple getMethods, propFindMethods and reportMethods 5 sessions are created when I expected only one to be created. Any further suggestions? Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had). I shall now recode based on your advice though - thank you for your help. Cheers Luke. - Quoting Ingo Brunberg [EMAIL PROTECTED]: Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. - 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: Slide Tomcat Sessions - Closing them
Hi, I did a bit more investigate and found I had made a mistake. It wasn't getHttpURL() that was creating a new session, it was the methods of WebdavResource that used the HttpURL I had got (for example reportMethod) that were causing a new session to be created. So, it seems it is not getHttpURL() that is creating the session, but instead methods such as reportMethod() that take a HttpURL as a parameter. Cheers Luke. - On 10 May 2004, at 18:15, Ingo Brunberg wrote: This is indeed worth investigating. Calling getHttpURL() should really not create a new session. Maybe you can post a code snippet? Ingo After a bit more investigation, it seems that constructing a new HttpURL or using the getHttpURL() method of WebdavResource also creates a new session. Should it be doing this? Is there a way to avoid it doing so? There are some cases where I can see no way of doing what I want without constructing a new WebdavResource or a HttpURL. Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hmm, either I misunderstood what you meant, or it doesn't quite fix things the way I expected. I now only construct one webdav resource in my code, however, after running just a few simple getMethods, propFindMethods and reportMethods 5 sessions are created when I expected only one to be created. Any further suggestions? Cheers Luke. - Quoting luke noel-storr [EMAIL PROTECTED]: Hi, I don't have a problem in terms of errors or crashes or anything; however, I was in fear of the rapidly increasing session count (into several thousands after just a few calls to a servlet I had). I shall now recode based on your advice though - thank you for your help. Cheers Luke. - Quoting Ingo Brunberg [EMAIL PROTECTED]: Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. - 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: Slide is a Document Manager?
Please copy me on code for this. We're looking at building a doc manager as well. Currently looking at JetSpeed and Liferay. Looks like JetSpeed is built on top of slide, so may be advantage to go with JetSpeed. Only issue there seems to be, at least to me, is that JetSpeed seems to take so long to come up. [EMAIL PROTECTED] 5/5/2004 7:13:45 AM Currently is solid like a prototype :-) it is not yet official but I can send you the code. -Original Message- From: Sez [mailto:[EMAIL PROTECTED] Sent: Wed 5/5/2004 8:57 AM To: 'Slide Users Mailing List' Cc: Subject:RE: Slide is a Document Manager? Ok, my base project is Jetspeed. I create a portal with jetspeed, but now, i need a document manager. It's interesting the new cms/doc man for Jetspeed... IS it a solid project? Where can I found it? -Mensaje original- De: Christophe Lombart [mailto:[EMAIL PROTECTED] Enviado el: dimecres, 5 / maig / 2004 07:37 Para: Slide Users Mailing List Asunto: Re: Slide is a Document Manager? Sezmillenium wrote: Hi pople! I want to know if slide is a document Manager. I want to save differents files from users. If any body knows some document manager (open source), it's also important. Slide is a good tools. It provides a Java API + a webdav folder but it better to used it via the Webdav layer. We (David and myself) are building new a CMS/doc management for Jetspeed which will be based on different content repo plugins in order to access to heterogenous content repository (based on different protocols). Default pluging are a webdav client and another one based on persitence component made by Scott for J2. Christophe Thanks SERGI - 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] Postmaster made the following annotations. -- This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: My Slide store implementation experience
Yes, please send copy to me also, if possible. I'd like to get my feet wet here. We also would like to look at writing a versioning system with slide/webdav layer above. Or at least understand how to display previous versions to users, that may already be stored in the history area. [EMAIL PROTECTED] 5/7/2004 4:50:20 PM Ty C wrote: As a developer who went through the experience I would like to suggest that the following will make my life easier: 1. Document how to write a Store (thoroughness about the interface would be most appreciated!) The thing that makes Java so easy to develop with is that the class libraries that come with the JRE (and JDK) are very well documented. 2. Document the data structures! In fact, I would very much appreciate calling a method with a descriptive identifier instead of figuring out that I have to put a (String, NodeRevisionNumber) into a Hashtable of latestRevisionNumbers. 3. This may come as a surprise: If there was a high-level interface that abstracted WebDAV with more raw operations, such as MOVE and MAKECOL, I would have preferred to write to that interface. As I am implementing a versioning filesystem, I had difficulty with the translation from PUT MAKECOL into NodeStore.createObject() ContentStore.createRevisionContent() in terms of knowing what was a file and what was a directory. I implemented this first creating object nodes as 0 length files in our document management system backend. Once I received a request to create an object as a child of this object, I transformed the 0 length file into a folder and then created the sub-child as a 0 length file.. Is there a better way? +1 on the above list! I'd love to use Slide for the WebDAV layer talking to my own store, but my last two efforts stranded in lack of time as I was trying to reverse-engineer the existing stores to extract the specs from them. Ty, if your store isn't too complex, I'd love to have a peek to see if I could use it as a starter for my own. Emile - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Postmaster made the following annotations. -- This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
newbie question - best resource/guides to programming with WebDAV?
What is best way/resource to get to break into this type of programming? I am a total newbie to this, and would like to know how to do the whole authentication/authorization thing using Apache/Slide and WebDav. Specifically, I've already got users and groups defined in an Oracle database, and would like to use this information to manage access to files under WebDav. This gets into the details of the applications that reside at application server/web server? I'm assuming that the webdav applications reside in the web server and are not like cgi scripts that are explicitly called from a get or post. Please verify, and forgive my newbieness. Thanks, Charlie ;) jl 5/10/2004 12:37:05 AM Hi Jeff! The WebDAV protocol does not contain any support for creating users. However Slide does have a way of solving this - if you use mkcol in you users collection, slide will automatically add DAV:principal element to the DAV:resourcetype property! Adding users to groups can be done using proppatch to set content of DAV:group-member-set. If you want to be these user to handle passwords too, the you have to user the SlideRealm in you tomcat server.xml /jacob - Original Message - From: J H [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 07, 2004 4:31 PM Subject: Create New Users Hi all, I'm trying to find some information on if the webdav protocol supports creating new users. What I'm trying to do is I'm building an applet which can browse documents, but I also want to create an admin tool, so that the administrator can assign users access to reports. It looks like to me that the application server (tomcat) is handling the authentication of users, but as of yet, I can't find anything on how to add users. Any ideas would be greatly appreciated, even correct keywords to search for on the net! :) Thanks, Jeff _ Mother's Day is May 9. Make it special with great ideas from the Mother's Day Guide! http://special.msn.com/network/04mothersday.armx - 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] Postmaster made the following annotations. -- This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Create New Users
Hi Jeff! The WebDAV protocol does not contain any support for creating users. However Slide does have a way of solving this - if you use mkcol in you users collection, slide will automatically add DAV:principal element to the DAV:resourcetype property! Adding users to groups can be done using proppatch to set content of DAV:group-member-set. If you want to be these user to handle passwords too, the you have to user the SlideRealm in you tomcat server.xml /jacob - Original Message - From: J H [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 07, 2004 4:31 PM Subject: Create New Users Hi all, I'm trying to find some information on if the webdav protocol supports creating new users. What I'm trying to do is I'm building an applet which can browse documents, but I also want to create an admin tool, so that the administrator can assign users access to reports. It looks like to me that the application server (tomcat) is handling the authentication of users, but as of yet, I can't find anything on how to add users. Any ideas would be greatly appreciated, even correct keywords to search for on the net! :) Thanks, Jeff _ Mother's Day is May 9. Make it special with great ideas from the Mother's Day Guide! http://special.msn.com/network/04mothersday.armx - 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]
Slide 2.0 - Webdav API Question / problem.
Hi !
Could someone explain me why the short piece of commented code here after
doesn't work ?
It seems that the Enumeration returned by getResources() contains null
elements within it as I could see in debug mode. Then I coded the good old
for loop trying to jump over the null elements. I could get the list of
elements (files and subdirectories). In fact the returned list by
listResources() is correct, there is in fact no need to check each element.
I wonder why the Enumeration contains nulls (getResourceNames() has the same
behaviour...).
Thanks for any hints !
Olivier
P.S. The webdav server is Slide2.0+Tomcat4.1.30
-
if (webdavResource.isCollection()) {
// Enumeration wdrs =
webdavResource.getChildResources().getResources();
// while (wdrs.hasMoreElements()) {
// WebdavResource resource = (WebdavResource)
wdrs.nextElement();
// recursivelist(resource.getPath());
// }
WebdavResource[] listOfResources =
webdavResource.getChildResources().listResources();
for(int i=0; i listOfResources.length; i++) {
WebdavResource wdr = listOfResources[i];
if (wdr != null) {
recursivelist(wdr.getPath());
}
}
}
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Slide Tomcat Sessions - Closing them
Hi, I posted a question a few days ago about Slide sessions within Tomcat not being closed, when using the client Java API. I didn't notice any replies so thought I'd post again under a different subject. Anyway, if anyone has experiences of trying to close sessions within Tomcat from within the client API then I'd be glad to hear about it. The .close() method of a WebdavResource doesn't seem to be working. (I'm currently using verion 2.0rc1 on the client side - does the final version fix this?). Cheers Luke. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide Compatibility
I am not sure if I am understanding you questions correctly, what do you mean when you say compatibility? Have you read the content of http://jakarta.apache.org/slide ?? To your question about character support then slide does support UTF-8. /jacob - Original Message - From: Renato Heeb [EMAIL PROTECTED] To: Slide Users Mailing List [EMAIL PROTECTED] Sent: Thursday, May 06, 2004 12:48 PM Subject: Slide Compatibility Hello, I've some newbie questions... sorry : ) -Where are the Notes about the Compatibility of slide? -Which webdav clients are tested using slide-webdav-server? -As it stands around Mac OSX as client? (I get many errors)--Are there some properties to set? -How does slide handle non ascii characters like(a,o,u)? Thanx for your informations and Links! - 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: Slide 2.0 - Webdav API Question / problem.
Hi,
maybe I don't get your point. You state that
- webdavResource.getChildResources().getResources() contains null elements
- webdavResource.getChildResources().listResources() is correct.
I would say that's not possible, because listResources() uses
getResources() internally and it does not check for null elements.
Also, if there really were null elements you surely would have gotten
a NullPointerException before.
Ingo
Hi !
Could someone explain me why the short piece of commented code here after
doesn't work ?
It seems that the Enumeration returned by getResources() contains null
elements within it as I could see in debug mode. Then I coded the good old
for loop trying to jump over the null elements. I could get the list of
elements (files and subdirectories). In fact the returned list by
listResources() is correct, there is in fact no need to check each element.
I wonder why the Enumeration contains nulls (getResourceNames() has the same
behaviour...).
Thanks for any hints !
Olivier
P.S. The webdav server is Slide2.0+Tomcat4.1.30
-
if (webdavResource.isCollection()) {
//Enumeration wdrs =
webdavResource.getChildResources().getResources();
//while (wdrs.hasMoreElements()) {
//WebdavResource resource = (WebdavResource)
wdrs.nextElement();
//recursivelist(resource.getPath());
//}
WebdavResource[] listOfResources =
webdavResource.getChildResources().listResources();
for(int i=0; i listOfResources.length; i++) {
WebdavResource wdr = listOfResources[i];
if (wdr != null) {
recursivelist(wdr.getPath());
}
}
}
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide Tomcat Sessions - Closing them
Do you actually have a problem with open sessions or is you interest rather theoretical? As I explained some time ago, you should use WebdavResource in such a way that you call a WebdavResource constructor only once in your application. This way you have no more than one connection, so you should hit no resource limits, hence my question above. The reason that WebdavResouce.close() does not really close the connection is that this would lead to having to reconnect if a parent or a child obtained by calling listWebdavResources() or getChildResources() issues the next request. You may call this a design deficiency, but this is how you are cuurently supposed to work with the client library. Ingo Hi, I posted a question a few days ago about Slide sessions within Tomcat not being closed, when using the client Java API. I didn't notice any replies so thought I'd post again under a different subject. Anyway, if anyone has experiences of trying to close sessions within Tomcat from within the client API then I'd be glad to hear about it. The .close() method of a WebdavResource doesn't seem to be working. (I'm currently using verion 2.0rc1 on the client side - does the final version fix this?). Cheers Luke. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
